@dnolen yea I figured that’s what should happen, but I’m not seeing where that would be enforced @ https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/compiler.cljc#L1438

@mikekap are you just curious or you’ve found a bug?

well i had a flaky build happen that said that cljs.test was missing symbols like report

seems unrelated

said build uses compile-root directly

right you’re on your own if you do stuff like that

just search cljs.closure for cljc, you’ll find code that chooses cljs over cljc

thanks - would it be worth filing the bug that compile-root doesn’t use those?

no

nothing in that namespace is public unless stated somewhere

if you want to see something be officially supported propose something for cljs.build.api

does cljs.compiler.api not qualify?

yes all the api namespaces qualify - you hadn’t said what you were using

also if you want this - a patch is most welcome 🙂

yes sorry - i am - the function is called compile-root in both api an non-api

ok sure

yes compile-root is naive, just grabs everything

Does cljs use vectors instead of clojure.lang.MapEntryies?

This is part of the same question: is there a way (in cljs) to differentiate between (second {:a 1 :b 2}) and [:b 2]

It appears that cljs uses cljs.core/PersistentVectors instead. So maybe they're indistinguishable?

@escherize isn’t that too low-level a distinction? In what way are you trying to differentiate between those two things?

@escherize not distinguishable - but not for any particular reason other then that was how it was originally implemented in CLJS

How do I call new on something that’s not a symbol, such as (.-ec elliptic)?

@pupeno I thought we relaxed this in the latest releases

I’m running 1.9.229

nah it's still there https://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/analyzer.cljc#L1660

I thought I had opened a JIRA ticket for that, but I can't find it

@dnolen oh we talked about it but I never did do anything it seems. As per our previous discussion, I'm going to close this: http://dev.clojure.org/jira/browse/CLJS-693 and open a new ticket for relaxing the symbol constraint

that sound good?

@anmonteiro go for it

@pupeno so you’ll just have to wait

ok, no problem @dnolen 🙂

@pupeno: FWIW, a workaround is store the result of that in a local var and call new on that instead

what’s the difference between (ns something.whatever (:require [this.between.brackets])) and (ns something.whatever (:require this.without.brackets))?

@rafaelzlisboa there's no difference AFAIK. Well, as shown by Stuart Sierra in https://stuartsierra.com/2016/clojure-how-to-ns.html there is a visual difference so vector is usually preferred :) > Put every :require’d namespace in a vector (square brackets) even if it doesn't have an :as or :refer. This makes visual scanning and sorting easier.

@rafaelzlisboa yes, no difference