https://issues.dlang.org/show_bug.cgi?id=12230
--- Comment #5 from Vladimir Panteleev <[email protected]> --- Well, for one thing, there is the inconsistence - if fields bind context, why don't methods? In much broader terms, I really really wish we'd have explicit control over alias context binding, at the instantiation site. Template aliases can allow for some very powerful things with a few small tweaks. I've written a serialization framework with almost zero overhead which depends on the compiler patches I wrote: https://github.com/CyberShadow/ae/tree/master/utils/serialization However, the compiler patches were not accepted so this is mostly defunct. For personal use I'm still using a patched compiler with PR #3884 reverted. I realize this is hypocritical of me because I argued a lot in favor of that PR (as a fix to code breakage), however I have come to depend on the behavior that PR reverted in my allocators library. I would like to some day make a case for these small language improvements, but I feel like it would be more wasted work. I almost went mad just from attempting to implement __traits(child) correctly. --
