Tip: always isolate macro libraries in independent project modules. Defining macros in modules that contain unrelated code (any code that is not strictly required for the macros to compile) is an anti-pattern that slows down compilation time.
Is the cause *only* that changes to the unrelated code result in large recompilations of macro expansions downstream? Or is there something more to it?
-
-
There is something more to it
News on what that is soon. -
can I subscribe to this tweet =)
End of conversation
New conversation -
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.