This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-11
Channels
- # admin-announcements (9)
- # arachne (1)
- # boot (125)
- # cider (5)
- # clara (34)
- # cljs-dev (11)
- # cljsjs (19)
- # clojure (164)
- # clojure-greece (7)
- # clojure-nl (2)
- # clojure-russia (5)
- # clojure-spec (3)
- # clojurescript (28)
- # clojurex (4)
- # core-async (3)
- # cursive (2)
- # datomic (3)
- # hoplon (268)
- # jobs (4)
- # keechma (2)
- # lambdaisland (1)
- # lein-figwheel (5)
- # leiningen (5)
- # off-topic (3)
- # om (3)
- # onyx (16)
- # re-frame (5)
- # reagent (31)
- # robots (1)
- # spacemacs (3)
- # specter (89)
- # untangled (1)
- # yada (26)
I’m surprised Closure would do this: https://github.com/google/closure-library/commit/bf758d3c2ef81b91e7d73608f68ee3c327b709d4
A consequence is that any ClojureScript code requiring goog.array.ArrayLike
will break with the next ClojureScript release. (Dunno if that’s actually important, but the principle of the matter seems important.)
Here’s another one. I suppose there’s just a mentality that doesn’t match my expectations (which I’ll revise): https://github.com/google/closure-library/commit/756182c7c566898ba0847d80b0c87389f7c037b6
@mfikes: they change the compiler and the library quite a bit, there’s not much we can do about it
Yeah. I’m accustomed to the Java platform model of striving to never break anything. I like the recent rant Rich is on about changing names.
Is it a known issue that in nashorn: before loading a namespace typeof my.existing.namespace.my_deffed_var => "object"
?
I looked in jira but couldn't find anything. Thought I would check here before filing an issue.