This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-14
Channels
- # aleph (10)
- # announcements (2)
- # beginners (228)
- # calva (18)
- # cider (6)
- # clara (5)
- # cljdoc (25)
- # cljs-dev (22)
- # clojure (78)
- # clojure-dev (30)
- # clojure-europe (2)
- # clojure-finland (1)
- # clojure-italy (32)
- # clojure-nl (21)
- # clojure-uk (126)
- # clojurescript (34)
- # cursive (5)
- # data-science (2)
- # datascript (2)
- # datomic (26)
- # defnpodcast (1)
- # emacs (5)
- # figwheel (5)
- # figwheel-main (3)
- # fulcro (14)
- # graphql (5)
- # jobs (1)
- # keechma (4)
- # nrepl (5)
- # off-topic (35)
- # onyx (3)
- # pedestal (12)
- # random (1)
- # re-frame (35)
- # reagent (8)
- # reitit (20)
- # remote-jobs (5)
- # ring-swagger (20)
- # shadow-cljs (166)
- # sql (43)
- # vim (6)
- # yada (15)
Maybe at some point it will make sense to begin porting https://github.com/clojure/spec-alpha2
We could revisit and decide whether to keep it in ClojureScript or whether it is started as a separate repo, or some code under main/cljs in that repo (presuming ClojureScript itself is sufficiently stable now to consider such a path)
Also if we do that, perhaps we have an opportunity to revise the alias used for stc
in cljs.spec.test.alpha2/check
to be consistent with what is used in Clojure (either exactly the same, or prefixed with cljs
)
so far it's nothing more than a fork with some renaming, but I guess that'll be a thing soon
If we attempt a separate implementation from ClojureScript proper, if it fails (because it just isn't working out), we could move it into ClojureScript proper
I can't recall the history, but it may have been the case that Spec was in Clojure proper when it was ported to ClojureScript.
Since the namespace name is something like clojure.spec-alpha2
we may not yet have to deal with the collision between the gen
var and namespace
Or, spec-alpha2
's Clojure design could be tweaked for portability to ClojureScript eliminating the collision
spec-alpha2 is the next version of spec and I’ve made a substantial commit this week (although changes are internal)
But I would wait till it settles before chasing it
far as I can tell that’s mostly about Clojure’s release cycle - which is not an issue we have
Perhaps because ClojureScript touches on so much “ecosystem” stuff, it will always need a shorter release cycle. (The Monday discussion.)
well we don’t have the release cycle adoption issue that Clojure has because of semantic versioning
Oh, I suppose we will encounter the gen
collision sooner. (I was wrong above.)
There exists a clojure.spec-alpha2.gen
namespace and a clojure.spec-alpha2/gen
var
Our old solution was to rename the namespace in the port to something like cljs.spec-alpha2.gen-impl
IIRC.
We have just upgraded our projects to the latest ClojureScript and enabled aot-cache and parallel-builds. On Windows we've noticed a bad interaction between these two flags. Either one on it's own works fine, but together we get a variety of strange compiler errors about redefining const, missing refers, e.t.c. Is there any known tickets for this? I couldn't see any