Fork me on GitHub

Any reason specs-alpha2 is in clojure.spec-alpha2 whereas spec-alpha is in



Alex Miller (Clojure team)19:11:47

but I donโ€™t have time to lay that all out atm


Iโ€™ll take your word for it ๐Ÿ™‚


I'm going to guess it has breaking changes compared to clojure.spec.alpha and therefore a new namespace is appropriate?

Alex Miller (Clojure team)20:11:08

yes, and having 3 .alpha namespaces is irritating :)


but the whole point of alpha is that there can be breaking changes

Alex Miller (Clojure team)20:11:56

yes, but in this case weโ€™re going to stick to non-alpha suggestions and make a new container instead

Alex Miller (Clojure team)20:11:18

there are lots of transition issues and having 2 things is going to make that easier

Alex Miller (Clojure team)20:11:40

suffice to say, Rich and I talked about it for a week and this made the most sense


it's tough when people use your stuff


Looks like a move to a much less macro-heavy, much more programmatic API? Great to see!


You have it in production yet? simple_smile


Don't! I'm already disappointed that we're "only" on Beta 4 of Clojure 1.10 in production. We have Beta 5 in QA but we've shifted our release schedule around to accommodate a couple of higher priority feature deployments ๐Ÿ™‚

Alex Miller (Clojure team)21:11:13

well the top api is still macros, it just inserts an intermediate non-macro layer


Yes, I should have worded that better... Still reading through the big commit splitting everything out... Nice work!

Alex Miller (Clojure team)21:11:45

more traumatic changes still in the queue :)


I look forward to creating a JIRA ticket at work for us to migrate from spec.alpha to spec-alpha2 ๐Ÿ™‚

Alex Miller (Clojure team)21:11:34

well, Iโ€™d wait a bit :)


Hah! You know me well ๐Ÿ™‚


Moving to spec-alpha2 is soo a couple of hours ago

๐Ÿ”ฅ 4

Why this particular scheme and not .alpha2? The inconsistency isn't important particularly, but it bothers me.


One thing that it provokes is a collision that would happen in ClojureScript between clojure.spec/gen the var and clojure.spec.gen the namespace. So in one minor way it is better.

๐Ÿ˜ข 4
Alex Miller (Clojure team)21:11:12

not really interested in bikeshedding the name, already did that

Alex Miller (Clojure team)21:11:16

the hope is to drive through another dev phase and reach a non-alpha point, which will necessitate a namespace change regardless

Alex Miller (Clojure team)21:11:18

my expectation is that most people will choose not to follow the gory parts of dev phase, but certainly would like to make it possible for interested parties to do so


I can see the value in having unique names for the various files in an editor (rather than several called alpha.clj).


If I find myself idle at work(!) I'll create a branch and see what it takes to get our 80K+ lines of code working with the new project (now that we're on deps.edn, it's easy for us to test against GitHub SHA branches etc ๐Ÿ™‚ )