What are the known pitfalls of std.typecons.Typedef as of now?

Things I know:

Have to use a cookie string to get a proper unique type.

Have to explicitly specify an init in order to specify a cookie.

Doesn't support "is" keyword.

Isn't nice to look at in error messages.

Relies on optimisations to alias itself away.

Are there any more?

On Saturday, 1 November 2014 at 23:18:35 UTC, John Colvin wrote:
> Doesn't support "is" keyword.

Another good use-case for allowing a user-defined operator for is.