On Thursday, 11 August 2016 at 20:27:01 UTC, Engine Machine wrote:
This requires F2 to know the future. It also forces it to use a
specific bar. I want inheritance like logic.
You are goind to hit a wall. Template programming is not OOP.
I'm not even sure that reflection would work in order to
determine the most "recent" overload.
Which is what we get when we mixin one deep, but when we go
deeper, it breaks. I think this is a bug. It seems like D is
trying to resolve things only after each mixin, rather than
resolving after all nested mixins are evaluated.
This is the only issue I see: "It seems like D is trying to...".
We need to know exactly what D does:
https://issues.dlang.org/show_bug.cgi?id=16376.
