On 2013-11-11 02:49, Timothee Cour wrote:
People have shunned proposals to have @mixin functions because it wouldn't be obvious at call site that some statement is executed under a mixin (which could access all variables in scope etc).The same will happen here; I think it should be clear at call site that a macro is used. How about: macro!myAssert(1 + 2 == 4); instead of myAssert(1 + 2 == 4);
I would really prefer if we not had to do that. -- /Jacob Carlborg
