With non-edn cropping up in the analysis cache it makes me even more curious what would happen if we had a spec for it

@mfikes would also be interesting to do that for the AST

would be useful for would be compiler hackers

heck, even for us who work on it all the time

One thing I liked about Bensu’s records was that it gave a little explicit structure that you could look at. Perhaps spec is a more direct way to do that. 🙂

@dnolen: are the new clojure predicates coming to CLJS as well? (the ones that make sense, ofc)

@anmonteiro: yes, if someone wants to make a patch I’m happy to apply it

should be pretty straightforward

@dnolen: I can do it but I think it’s better to wait at least until the alpha is released?

@anmonteiro: there’s no need to wait

I probably won’t cut a release till after the next Clojure alpha anyway

need to fix the transit cache issues, so probably Friday at the earliest

gotcha

@dnolen are you open to a predicates test ns like in clojure?

@anmonteiro: already offered to port those

ok

and yes pretty much anything added to Clojure around clojure.spec is on the table for ClojureScript cljs.spec

sorry i didnt read the thread, just signed on

@pat: go ahead and make the patch if you want

I’ve been busy so I haven’t even opened the JIRA issue

are you sure? I havent written anthing yet

yea go ahead

@pat do you have your CA filed?

@anmonteiro: thanks will do @dnolen yes

cool then go for it, would prefer to get a patch that simply covers all of Clojure commit 58227c5

over anything piecemeal

Including spec stuff?

i ask only because I haven't studied it yet, but i'll take a crack at it

@pat that’s really the only thing I’m interested in

the entire commit

ok!

fortunately there’s not too much study here, mostly just copy and pasting into the appropriate spots

that is this doesn’t really require understanding how spec works

if you do have a question about something, ask it’ll likely be simple

ok

http://dev.clojure.org/jira/browse/CLJS-1672

@pat thanks, I fixed your permissions in JIRA you should be able to do whatever you need to that ticket (or any other ticket)

awesome thankyou