@dnolen: Summary on cljs.spec for self-host: http://dev.clojure.org/jira/browse/CLJS-1652 was the only thing I was able to find (so I don’t have a slew of other changes to coalesce with it). I haven’t delved into the test.check / generator aspect yet. I’ll need to apply http://dev.clojure.org/jira/browse/TCHECK-105 to a custom build and see how far I can get with it.

@dnolen: ./script/build is failing for me because there’s no v1.9 tag, from what I gather

should I build against a commit previous to 1.9?

@anmonteiro: hrm I pushed the tag

did you run git fetch —tags ?

maybe I didn’t fetch it

let me try

yea I hadn’t fetched the tag, sorry for the noise

np

spec generators work in bootstrap. There are some bumps and some things fail as being undefined, but some basic stuff actually works. (The failures could very well be bugs in downstream Planck, FWIW.) https://twitter.com/mfikes/status/736908445316681728

One thing I wonder is whether it is intentional that impl appear in the namespace.

@mfikes yes intentional

there’s a clash between cljs.spec/gen and cljs.spec.gen

that is, a var would match a namespace otherwise and one would overwrite the other

is there a way to get at the clojurescript-version? cljs.util/clojurescript-version would seem useful but the ns can’t be imported in CLJS

(because of )

@anmonteiro: *clojurescript-version*

yea that works

missed that, thanks

https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/core.cljs#L16

@dnolen: Whoa. Already reached zero known bugs in spec bootstrap. Everything is working AFAIKT.

@mfikes: nice!