This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-26
Channels
- # aws-lambda (2)
- # beginners (10)
- # boot (17)
- # cider (19)
- # clara (1)
- # cljs-dev (13)
- # cljsjs (22)
- # cljsrn (1)
- # clojure (132)
- # clojure-austin (2)
- # clojure-berlin (2)
- # clojure-dusseldorf (1)
- # clojure-germany (2)
- # clojure-italy (7)
- # clojure-spec (6)
- # clojure-uk (5)
- # clojurescript (45)
- # core-matrix (3)
- # cursive (4)
- # datomic (8)
- # emacs (3)
- # keechma (3)
- # lein-figwheel (1)
- # leiningen (2)
- # lumo (24)
- # nyc (1)
- # off-topic (29)
- # om (68)
- # onyx (5)
- # perun (50)
- # planck (5)
- # protorepl (5)
- # re-frame (128)
- # reagent (10)
- # remote-jobs (1)
- # ring (4)
- # rum (41)
- # untangled (28)
- # yada (4)
I've just been bitten by http://dev.clojure.org/jira/browse/CLJS-1868 There's a patch there already, is there anything I can do to help make it easier to move things along? It would be my first time contributing so I don't really know what I'm doing yet but I have signed the CA. I also do CLJS work regularly on both Windows and Mac.
wrt. CLJS-1954, just filed https://github.com/google/closure-compiler/issues/2336 in the Google Closure Compiler
It's not clear to me that this is a ClojureScript issue
I’m afraid we cannot wait for them to release a new closure-compiler version. Either we have to revert Feb2017 version or somehow work around it on our side.
I don't know what the problem is
@darwin what's the urgency that you can't continue using 1.9.473?
@anmonteiro that’s a solution, but anyone updating and compiling core.async dependent project in advanced mode will see this, it is not obvious this was caused by the update
at least in my case it took several hours between bumping clojurescript dependency and getting to compile it affected code under advanced mode, it worked just fine under :none
At least we have a ticket that explains it
It's not like we can go back and revert the releas
It's out there forever