https://gist.github.com/sgrif/7e28000d05f43899e68346f0f00d20a9 … is obviously the most pathological example. But I think it's way more insidious. If we let these functions call any code that was generated by a macro we're leaking compiler internals, since they're now dependent on order of evaluation
-
-
The first one is of course "solvable" by hygiene based on execution order, but you are right, that does de facto stabilize execution order of the compiler. Which might not even be deterministic using a query-based compiler implemention
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.


