Clojurians
#cljs-dev
<
2017-02-26
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

shaun-mahood00:02:58

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.

anmonteiro05:02:42

wrt. CLJS-1954, just filed https://github.com/google/closure-compiler/issues/2336 in the Google Closure Compiler

anmonteiro05:02:55

It's not clear to me that this is a ClojureScript issue

darwin13:02:22

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.

anmonteiro17:02:05

I don't know what the problem is

anmonteiro17:02:37

@darwin what's the urgency that you can't continue using 1.9.473?

darwin17:02:18

@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

darwin17:02:06

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

anmonteiro17:02:09

At least we have a ticket that explains it

anmonteiro17:02:36

It's not like we can go back and revert the releas

anmonteiro17:02:47

It's out there forever

darwin17:02:37

right, I’m not saying reverting existing release, I’m asking for a new release

darwin17:02:16

anyways, I now agree it is not that urgent as I originally thought, if you know what is going on