This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-13
Channels
- # admin-announcements (208)
- # beginners (53)
- # boot (46)
- # cider (10)
- # cljs-dev (26)
- # cljsjs (10)
- # clojure (66)
- # clojure-dev (3)
- # clojure-russia (14)
- # clojurecup (5)
- # clojurescript (302)
- # cursive (22)
- # data-science (1)
- # datomic (10)
- # emacs (1)
- # events (2)
- # hoplon (91)
- # incanter (1)
- # ldnclj (3)
- # leiningen (1)
- # off-topic (2)
- # om (41)
- # re-frame (40)
- # reagent (78)
Are the ops supported cljs.analyzer/parse
the ClojureScript special forms? That would mean they are { var
, if
, case*
, throw
, try
, def
, fn*
, letfn*
, do
, let*
, loop*
, recur
, quote
, new
, set!
, ns
, deftype*
, defrecord*
, .
, js*
}
@mfikes: yes in that there have to be parse cases for special forms. There may be some additional internal cases in the future.
I wonder if Clojure preserves the order of libs in an ns
form. (I failed to empirically show that it doesn’t—something that can be done for ClojureScript.)
One thing to ponder: What if textual order in an ns
form is inconsistent with the partial order induced by the existing :requires
in the dependent namespaces.
if you cannot reason about than the occasionally top level side effectful thing can’t be done
Wrt my last comment: Perhaps if it simply does what Clojure does today, it all pans out.
I would inc dnolen - given that namespace loading can have side effects it makes no sense for ordering not to matter to me
Hi, I guess alter-meta! only works on atoms in clojurescript, right? Would a pull request to fix the docstring be considered? https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/core.cljs#L9120