@borkdude if $macros
is used directly that would be an error. it is what the self-hosted stuff uses for macros but the user should access directly
just like regular CLJS can't reach into CLJ directly
@thheller this is used in cljs.spec
so maybe it's only an implementation detail, but at least now implementors don't get a false positive 😉
or should that namespace have been explicitly required / aliased?
hmm right that looks like its working around resolve issues where you can't otherwise reference something from the macro world directly