@mfikes: regarding the comment you left in http://dev.clojure.org/jira/browse/CLJS-1474

I suspect that even if we make that a warning we’ll still see it in bootstrap CLJS which might be undesirable

Right

I’m only now starting to look at what might be going wrong, but there should probably be a way around this

I also wonder if funky stuff will happen by using defmacro def in bootstrap

or any other special form, for that case

I can't recall if I tried the patch in regular ClojureScript—expanding the def macro would seemingly lead to a def def. Hmm...

proposal: don’t employ this check if we’re evaluating a form in a namespace that ends with $macros

(obviously) all tests pass if the above proposal is applied

proposal: def on a special form is legal, only triggering a warn. Introduce a mechanism to suppress warnings (à la :warnings) within specific scopes (perhaps via meta or set!), and then suppress it for (defmacro def instance in cljs.spec.

sounds more reasonable to me than what I proposed