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

clojure.spec.alpha?

yes

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?

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

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

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

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

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

https://github.com/clojure/spec-alpha2/compare/11d21c5f055f49b6a84554837b80c91be831c058...master for those curious to see what's different 🙂

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

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!

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 🙂

well, I’d wait a bit :)

Hah! You know me well 🙂

Moving to spec-alpha2 is soo a couple of hours ago https://github.com/slipset/speculative/tree/spec-alpha2

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.

not really interested in bikeshedding the name, already did that

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

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 🙂 )