Fork me on GitHub
#clojure-dev
<
2018-11-14
>
slipset19:11:04

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

slipset19:11:11

clojure.spec.alpha?

alexmiller19:11:47

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

slipset19:11:16

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

seancorfield20:11:31

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

alexmiller20:11:08

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

gfredericks20:11:17

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

alexmiller20:11:56

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

alexmiller20:11:18

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

alexmiller20:11:40

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

gfredericks20:11:49

it's tough when people use your stuff

seancorfield21:11:18

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

shaun-mahood21:11:13

You have it in production yet? simple_smile

seancorfield21:11:13

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 ๐Ÿ™‚

alexmiller21:11:13

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

seancorfield21:11:48

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

alexmiller21:11:45

more traumatic changes still in the queue :)

seancorfield21:11:14

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

alexmiller21:11:34

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

seancorfield21:11:49

Hah! You know me well ๐Ÿ™‚

slipset21:11:06

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

๐Ÿ”ฅ 1
dominicm21:11:09

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

mfikes21:11:09

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.

๐Ÿ˜ข 1
alexmiller21:11:12

not really interested in bikeshedding the name, already did that

alexmiller21:11:16

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

alexmiller21: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

seancorfield22:11:47

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

seancorfield22:11:18

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 ๐Ÿ™‚ )