Re: [ANN] Clojure 1.9 / clojure.spec split

2017-05-21 Thread Matching Socks
> Additionally, this is a first step towards increased support for leveraging dependencies within Clojure. What do you have in mind? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-05-04 Thread Steve Miner
> On May 3, 2017, at 7:37 PM, Alex Miller wrote: > > A newer version (0.1.108) of spec.alpha is available that fixes the issue. > Note that this kind of update is exactly why the jars are split - you can > update the libs more frequently than the Clojure version. Thanks.

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-05-03 Thread Alex Miller
Going forward, you will need to create your classpath with three jars: Clojure, spec.alpha, and core.specs.alpha. There are some more things planned in this area still to come. We do not currently plan to build a combined jar but things may change. The web page in question will be updated when

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-05-03 Thread Steve Miner
Before the spec split, the basic way to invoke Clojure at the command line was: % java -cp clojure.jar clojure.main Documented here: https://clojure.org/guides/getting_started Is that still the intended usage with 1.9 going forward? When I try it

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-27 Thread Alex Miller
On Thursday, April 27, 2017 at 3:05:26 AM UTC-5, Tamas Herman wrote: > > What problems would it pose if the alpha status would be reflected in the > version number of org.clojure/spec, > just like it is the case with org.clojure/clojure rightnow, which is > 1.9.0-alpha15? > At some future

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-27 Thread Tamas Herman
What problems would it pose if the alpha status would be reflected in the version number of org.clojure/spec, just like it is the case with org.clojure/clojure rightnow, which is 1.9.0-alpha15? I've seen the Spec-ulation Keynote from Rich and this step feels like an experiment to try out the

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Sean Corfield
I switched the World Singles’ codebase over to using org.clojure/spec.alpha today with no problems. Since we always `:require .. :as` it was an easy global find’n’replace (well, three of them – one for each namespace change needed). We’re also explicitly depending on the 0.1.94 release (so our

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Alex Miller
I guess I should say again that no one needs to depend directly on these - Clojure will include them via dependency. At some point there will may be a newer version of these libs you wish to use than the one included by Clojure and only in that case would you need to include it directly. On Wed,

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Alex Miller
[org.clojure/spec.alpha "0.1.94"] [org.clojure/core.specs.alpha "0.1.10"] are available now. On Wednesday, April 26, 2017 at 1:28:05 PM UTC-5, Sean Corfield wrote: > > Whilst this is rather disruptive for current users of clojure.spec, I > understand and appreciate the goal. > > > > I hope

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Alex Miller
On Wednesday, April 26, 2017 at 6:27:08 PM UTC-5, Colin Fleming wrote: > > Doesn't this mean that Clojure and spec will be mutually dependent, i.e. a > dependency cycle? > Yes > Is that likely to cause problems for any tooling? > No? :) Feedback wanted, though if you find that to not be

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Colin Fleming
Doesn't this mean that Clojure and spec will be mutually dependent, i.e. a dependency cycle? Is that likely to cause problems for any tooling? On 27 April 2017 at 06:27, Sean Corfield wrote: > Whilst this is rather disruptive for current users of clojure.spec, I > understand

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Sean Corfield
Whilst this is rather disruptive for current users of clojure.spec, I understand and appreciate the goal. I hope that the new org.clojure/spec.alpha will be made available for a few days ahead of actually removing it from Clojure 1.9 so that those of us already using it and doing

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Alex Miller
On Wednesday, April 26, 2017 at 11:32:39 AM UTC-5, Leon Grapenthin wrote: > > Thanks for the update, this seems like a good decision allowing things to > evolve more quickly. > > Does that also mean that there are no breaking changes intended to current > non .alpha namespaces/APIs? > 1.9

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Leon Grapenthin
Thanks for the update, this seems like a good decision allowing things to evolve more quickly. Does that also mean that there are no breaking changes intended to current non .alpha namespaces/APIs? Kind regards, Leon On Wednesday, April 26, 2017 at 5:30:56 PM UTC+2, Alex Miller wrote: > >

Re: [ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Tatu Tarvainen
Thanks for the update. This seems like a good decision that moves Clojure forward without tying your hands as to the future direction of spec. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to

[ANN] Clojure 1.9 / clojure.spec split

2017-04-26 Thread Alex Miller
We are moving spec out of the Clojure repo/artifact and into a library to make it easier to evolve spec independently from Clojure. While we consider spec to be an essential part of Clojure 1.9, there are a number of design concerns to resolve before it can be finalized. This allows us to