Enjoyed your talk! about golgi HOT 1 CLOSED

Hi Jeff, thanks for the kind words.

The explicit error state/message is there due to the fact that Haxe doesn't really have order-of-evaluation guarantees for macro code, and having two classes involved in a build macro can really throw some cryptic errors... it's possible to reference a child/dependent class before the parent has been completely resolved for instance. Here's some relevant tidbits from the manual : https://haxe.org/manual/macro-limitations-build-order.html

I'm still working on this, and I might find a way around it, but for now the safest thing to do is prevent macro-built classes from sharing modules with each other or their dependent types.

Also, as a heads up, I talked with NC and Juraj and will likely tweak the protocol a bit based on their suggestions. It shouldn't be too drastic, and your code should still work after some simple and obvious fixes.

Stay tuned, and thanks for giving it a shot!

from golgi.