On Thursday, June 2, 2016 at 10:05:59 AM UTC-5, Leon Grapenthin wrote:
> Until now impl was a convention to indicate that the vars the ns is private
> to the library itself. I belive that the pattern became more common with
> core.async.
Thanks for the background context on `impl`, Leon.
--
No
Until now impl was a convention to indicate that the vars the ns is private to
the library itself. I belive that the pattern became more common with
core.async.
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because yo
The namespace cljs.spec.gen would clash with the existing var
cljs.spec/gen. The ClojureScript compiler will warn about this when it
happens.
On Thu, Jun 2, 2016 at 9:41 AM, Shaun LeBron
wrote:
> Oops, I missed that, thanks!
>
> Why is it under `impl`? I'd actually like to read about what the
>
Oops, I missed that, thanks!
Why is it under `impl`? I'd actually like to read about what the philosophy
behind `impl` is since it's been turning up a lot.
On Thursday, June 2, 2016 at 8:33:06 AM UTC-5, Mike Fikes wrote:
> Hey Shaun,
>
> It has been. It is cljs.spec.impl.gen
>
> - Mike
>
> >
Hey Shaun,
It has been. It is cljs.spec.impl.gen
- Mike
> On Jun 2, 2016, at 9:32 AM, Shaun LeBron wrote:
>
> Great stuff, thanks! I'm not familiar, but is the `clojure.spec.gen`
> namespace going to be ported?
>
> On Wednesday, June 1, 2016 at 1:01:58 PM UTC-5, David Nolen wrote:
>> Clojur
Great stuff, thanks! I'm not familiar, but is the `clojure.spec.gen` namespace
going to be ported?
On Wednesday, June 1, 2016 at 1:01:58 PM UTC-5, David Nolen wrote:
> ClojureScript, the Clojure compiler that emits JavaScript source code.
>
>
> README and source code: https://github.com/clojur
No. This only about the convenience of aliasing core common namespaces that
only differ by name between Clojure and ClojureScript.
David
On Thu, Jun 2, 2016 at 12:19 AM, Herwig Hochleitner
wrote:
> 2016-06-02 4:54 GMT+02:00 David Nolen :
>>
>> We are considering aliasing support for cljs.spec.
2016-06-02 4:54 GMT+02:00 David Nolen :
>
> We are considering aliasing support for cljs.spec. That is rewriting
> clojure.spec vars in ClojureScript sources to cljs.spec but it will likely
> cover more than just cljs.spec - cljs.test, cljs.pprint etc.
>
Interesting. Is this on the table as a gene
Choosing cljs.spec over clojure.spec is out of necessity not preference -
Clojure has already taken the namespace and that namespace defines macros.
We are considering aliasing support for cljs.spec. That is rewriting
clojure.spec vars in ClojureScript sources to cljs.spec but it will likely
cover
Would it be good to change the namespace for spec from cljs.spec to
clojure.spec? This will make CLJC files nicer to write as you won’t need to
have reader conditionals for requiring cljs.spec in CLJS and clojure.spec
in CLJ.
It seems like spec is going to be used by lots of projects, so the choic
It's like magic. I added some specs to cljc namespaces and it just works!
I'm making domain specific error messages with just a few lines of code.
This is a huge leap forward.
Thank you, and all involved, so much.
--
Note that posts from new members are moderated - please be patient with your
11 matches
Mail list logo
