One step out of the TypeInfo stalemate

[Paul Backus]

On Tuesday, 28 July 2020 at 20:37:19 UTC, Alexandru Ermicioi 
wrote:
> That would make typeinfo hierarchy a lot cleaner.
> Having type known in typeinfo object would also allow 
> implementation of reflection methods as members which in turn 
> would make reflection based code much much cleaner from 
> developer perspective.
>
> For example currently to check if member is present on type T 
> we have to do smth like:
>
> __traits(hasMember, T, "member")
>
> When it can be more readable through typeid statement like:
>
> typeid(T).hasMember!"member"

Well, just about anything is better than the current __traits 
syntax. IMO an easy improvement would be to provide some syntax 
sugar so you could write

     T.__hasMember("member")

and the compiler would lower it to

     __traits(hasMember, T, "member")