Re: [ClojureScript] GCL advanced compilation bug-- :foo-bar and :foo_bar both become :foo_bar

These are all the same issue. Fixed in master and will be fixed in the next release. In the meantime you should be able use to use `:optimize-constants false` in your build settings to avoid this for now. David On Fri, Mar 13, 2015 at 6:01 AM, Michiel Borkent wrote: > I have run into an issue i

Re: [ClojureScript] GCL advanced compilation bug-- :foo-bar and :foo_bar both become :foo_bar

I have done some further testing and I think this was the same issue. PS: the data used was not an EDN literal, but was dynamically created. On Friday, March 13, 2015 at 11:01:40 AM UTC+1, Michiel Borkent wrote: > I have run into an issue in advanced mode when accessing a map with a keyword >

Re: [ClojureScript] GCL advanced compilation bug-- :foo-bar and :foo_bar both become :foo_bar

I have run into an issue in advanced mode when accessing a map with a keyword that contains an underscore: https://gist.github.com/borkdude/be911f120c1676108644 I'm not sure if that is also fixed by CLJS-1105? On Friday, March 13, 2015 at 1:40:33 AM UTC+1, Mike Fikes wrote: > Perhaps the same:

Re: [ClojureScript] GCL advanced compilation bug-- :foo-bar and :foo_bar both become :foo_bar

Perhaps the same: http://dev.clojure.org/jira/browse/CLJS-1105 Fixed with a recent commit: https://github.com/clojure/clojurescript/commit/4bcc95175e4282d43ed74bf0abd670550fc40140

[ClojureScript] GCL advanced compilation bug-- :foo-bar and :foo_bar both become :foo_bar

If you have two identically named keywords, one being dash separated and the other being underscore separated, both will come out as underscore separated after getting run through advanced mode compilation and only in advanced mode. The I'm posting this here because I'm unsure if it's a bug in Cloj