Re: template class name unconsistent behavior

[timotheecour]

If this behavior is not a bug, I wonder what's the rationale, but 
also, how can we have such a "make" function that doesn't mess up 
the template class name depending on the order of which is used 
first (the make!T variant or the new A!T) ?