Challenge

[Daniel N via Digitalmars-d]

On Wednesday, 5 October 2016 at 02:15:13 UTC, Jonathan M Davis 
wrote:
> The AliasSeq muck is there because for some reason you can't 
> alias the result of __traits, so doing something like
>
> alias sym = __traits(getMember, T, member);
>
> isn't legal. So, this has nothing to do with a recommendation 
> of best practice and everything to do with an annoying bug.
>

When aliasing a single symbol, I find it much cleaner to use...
Identity!(...) or I!(...)
... instead of
AliasSeq!(...)[0]