@thheller the form in the warning has reader meta data on it so it's "possible" to get this data

is it? couldn't find any in this case

but my attempt so far war very naive, just collecting the warning info

eventually I will hook into the actual analyzer

current looking into how I could potentially leverage clojure.core.specs stuff

since I assume that will come to CLJS at some point as well

(defn x :foo) yields rather useless exception in CLJS

and a nicer but still not very useful spec error in CLJ

exactly

Since there has been a long debate on isolation and not polluting target, here is a solution: https://gist.github.com/cgrand/259fa9ee3553d642850501ed431fc74d

Basically it creates isolated clojure envs inside the JVM, and the only way to talk to these envs is through a pair of streams.

@cgrand nice, it reminds me of boot's pods