This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-25
Channels
- # aws (2)
- # bangalore-clj (2)
- # beginners (90)
- # boot (89)
- # bristol-clojurians (1)
- # cider (23)
- # cljs-dev (48)
- # cljsjs (2)
- # cljsrn (3)
- # clojure (118)
- # clojure-argentina (3)
- # clojure-austin (8)
- # clojure-czech (1)
- # clojure-dev (18)
- # clojure-ireland (1)
- # clojure-italy (4)
- # clojure-russia (6)
- # clojure-spec (75)
- # clojure-uk (224)
- # clojurescript (103)
- # core-async (28)
- # cursive (3)
- # datascript (7)
- # datomic (15)
- # dirac (30)
- # emacs (14)
- # events (3)
- # figwheel (1)
- # hispano (1)
- # hoplon (176)
- # lambdaisland (1)
- # lein-figwheel (6)
- # off-topic (21)
- # om (7)
- # onyx (2)
- # pedestal (6)
- # re-frame (4)
- # reagent (15)
- # spacemacs (67)
- # specter (13)
- # testing (9)
- # untangled (65)
- # vim (6)
- # yada (1)
I added a comment on http://dev.clojure.org/jira/browse/CLJS-1792, it looks like the patch would be trivial, but it surely has something that I am overseeing 😄
Is there any interest in http://dev.clojure.org/jira/browse/CLJS-1841? It would improve the onboarding flow for new contributors getting setup
@danielcompton I applied and it an immediately ran into some problem
I'm just checking itnow
I'll give it a workout against master
if you have time might want to give master a spin - I just landed this https://github.com/clojure/clojurescript/commit/94b4e9cdc845c1345d28f8e1a339189bd3de6971
IIRC there were some other issues that were blocked because of that one?
that can now be worked on? or am I confusing with something else?
@dnolen Something in that commit is breaking Planck… will try to sort out what it might be
interesting, trying it out in Lumo
OK… (for Planck it is breaking the build phase where it AOT-compiles its macro namespaces), but I’ll check for any load-libs
calls.
@mfikes is it that specific commit?
or could it be related to the recent spec fixes?
(since you AOT clojure.spec macros)
I’m pretty sure it is that commit… I’ve been very closely following master as of late and it was good with the previous commit
sure, just confirming
I haven't been following it too closely
FWIW, script/test-self-parity
fails with something related to ns
processing:
#error {:message "Could not parse ns form cljs.clojure-alias-test", :data {:tag :cljs/analysis-error}, :cause #object[Error Error: No protocol method IDeref.-deref defined for type null: ]}
@dnolen now with master, Planck’s tests pass. I still get the same failure with script/test-self-parity
. Perhaps there is a weakness in the test. I’ll take a look at it tonight (heading out for dinner)
self parity tests still fail for me with current master
but Lumo compiles correctly, which it didn't with HEAD1~
scratch that, Lumo doesn't compile with current master
gets stuck while AOTing macros
I don't have time to look into it now, but I suspect that if we get the self parity tests to pass everything will be OK downstream in Planck & Lumo
Oops, should have run all the suites, sorry about that.
I've updated http://dev.clojure.org/jira/browse/CLJS-1841, ready for someone else to take a look