Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Cool!! Sent from my mobile Original Message From:Nikita Prokopov Sent:Sun, 25 Sep 2016 11:52:19 +0300 To:Clojure Subject:Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8 >Matan, > > >spec is pretty isolated part

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Matan, spec is pretty isolated part of Clojure, so it’s basically a copy-paste job with couple of gaps filled in that were introduced in 1.9. Updating it is basically getting diff from clojure and applying it to my repo. Sometimes with some manual corrections. Nikita. On Sat, Sep 24, 2016 at

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Nikita, this is cool, e.g. as lighttable does not yet fully support 1.9. Can you say something about how are these backports derived? so that I can get an intuition into how much it is at par with the real thing? Does it involve a lot of code rewrite to backport each 1.9 alpha version? On

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Did you read my whole question? It doesn't work to have the implementation namespace require the spec namespace either, as I demonstrated in my second example, where the spec for the factor function uses the prime? predicate. On Friday, July 1, 2016 at 1:38:23 AM UTC-4, Sean Corfield wrote: > >

RE: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

I can’t help but think you’re making it way more complicated than it needs to be. Define ::config in example.spec, and in example.core use :example.spec/config (and, yes, require the example.spec namespace). You need to avoid circular namespace dependencies. Sean Corfield -- (904) 302-SEAN An

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

I spent quite a while trying to figure out how I can use some features of spec, like destructuring, to work properly when my specs are in a separate namespace. I asked a question about this on Stack Overflow; do you have any advice on how to solve

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Thanks Sean. You make an excellent point with specs being in a separate namespace. I had thought that using fdef would have prevented doing something like this but it appears I am wrong. On 30 June 2016 at 01:20, Sean Corfield wrote: > On 6/29/16, 10:03 AM, "Lucas Bradstreet"

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

On 6/29/16, 10:03 AM, "Lucas Bradstreet" wrote: > Sean, a lot of library developers still want to support Clojure 1.8, > but this would prevent using spec with their projects. clojure.java.jdbc solves that by having the specs in a

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

This looks great Nikita. Sean, a lot of library developers still want to support Clojure 1.8, but this would prevent using spec with their projects. This would help there. Onyx in particular was going to avoid using spec for the time being, but we may re-evaluate now. On 30 June 2016 at 00:31,

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Interesting idea. If you’re already on Clojure 1.8, I think it’s pretty safe to upgrade to the Alpha builds of 1.9. We’re running 1.9 Alpha 7 in production at the moment (and will move to Alpha 8 in our next build after today). The only glitches we ran into were name collisions in

[ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Hi! Not sure if a good idea or bad, but if you were eager to play with latest version of clojure.spec but don’t want to upgrade your production to alpha version of the language, you can add clojure.spec capabilities as a library to 1.8: https://github.com/tonsky/clojure-future-spec