This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-15
Channels
- # beginners (6)
- # cider (13)
- # cljs-dev (45)
- # cljsrn (1)
- # clojure (11)
- # clojure-france (1)
- # clojurescript (13)
- # cursive (19)
- # data-science (10)
- # datascript (1)
- # datomic (2)
- # docs (8)
- # fulcro (26)
- # graphql (1)
- # hoplon (2)
- # jobs (1)
- # off-topic (5)
- # parinfer (21)
- # re-frame (2)
- # reagent (22)
- # shadow-cljs (3)
- # spacemacs (8)
- # unrepl (1)
@bhauman well I’m going to see New Orleans now, keep me posted if this is working for you or if you have some other ideas
@dnolen for when you have time I would to ask you one thing. I see here https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/js.cljs#L176
that the code that assoc-in
uses name
. For an generic statement/expression though, name
is usually not really significant and while we could make document that says that name
has to be munged because it will end up in :source-maps
, I see that you are already doing it the same in https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/js.cljs#L161
I was then wondering whether the code should use that smn
for the key in :source-maps
. Ready for patching if necessary.
the fact that name
is used for source maps needs to be documented nonetheless
Uhm I wonder if I actually need to disable source maps when evaluating expressions at the REPL and if js.cljs
is taking care of updating the right thing only when it "sees" an ns
form
that of course would be a nice to have, as you could run the watcher and share the env/compiler with the repl ala figwheel
kind of difficult to reconcile that without changing clojure.main
semantics - and -c
doesn’t make much sense as a init
option
hmm what about allowing multiple main options (i.e -c
and -r
) in this case as it is a very sensible case
@bhauman actually allowing -r
to be non-terminal really is a problem, since that would prevent a user from doing something intentional