This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-27
Channels
- # aws (19)
- # babashka (47)
- # beginners (111)
- # boot (3)
- # bristol-clojurians (3)
- # chlorine-clover (2)
- # cider (13)
- # cljs-dev (8)
- # clojure (143)
- # clojure-europe (11)
- # clojure-germany (10)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (1)
- # clojure-spec (6)
- # clojure-survey (3)
- # clojure-uk (42)
- # clojurescript (229)
- # conjure (131)
- # cursive (21)
- # data-science (18)
- # datomic (4)
- # emacs (21)
- # events (2)
- # figwheel-main (12)
- # fulcro (18)
- # graalvm (1)
- # hoplon (40)
- # jobs (1)
- # joker (17)
- # kaocha (1)
- # lambdaisland (1)
- # off-topic (19)
- # rdf (7)
- # re-frame (31)
- # reagent (26)
- # reitit (20)
- # rum (4)
- # shadow-cljs (106)
- # sql (17)
- # testing (5)
- # vim (2)
re: allow requires from the global namespace could work for other useful JS targets too, Rhino/Nashorn/Graal.js https://clojure.atlassian.net/browse/CLJS-3233
after auditing some React Native stuff, I think one level for property access for namespaces is too restrictive, being able to access NativeModules needs at least two levels, but likely more https://clojure.atlassian.net/projects/CLJS/issues/CLJS-3235
why not a .
for the second case? then $
has the clear meaning of separating <source>$<export>.<property>
vs having two meanings depending in on the place it it used in?
and $
might actually be used inside variable names too so it removes that clash possibility
With CLJS-3235 in place would this also mean that "symbols" within objects now appear in the compiler state? If so it would be huge cause we can finally complete them 😄