On Thursday, 20 March 2014 at 12:31:33 UTC, Manu wrote:
I'm sorry. I really can't support any of these wildly complex
ideas.
They aren't actually complex, except tail-call optimization (but
that is well understood).
If you want to inline a second level, then write mixin in the
second level.
You might as well do copy-paste then. You cannot add inlining to
an imported library without modifying it.
at all, which is annoying, because I REALLY need this (I've
been trying to
motivate inline support for over 3 years), and I get the
feeling you're
just throwing hypotheticals around.
You need inlining, agree, but not 1 level mixin. Because you can
do that with regular inlining.
