This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-10
Channels
- # admin-announcements (2)
- # alda (16)
- # beginners (22)
- # boot (55)
- # cider (11)
- # cljs-dev (5)
- # cljsrn (7)
- # clojure (115)
- # clojure-art (1)
- # clojure-finland (3)
- # clojure-greece (18)
- # clojure-madison (2)
- # clojure-norway (2)
- # clojure-poland (50)
- # clojure-russia (122)
- # clojure-uk (9)
- # clojurescript (28)
- # core-async (7)
- # cursive (4)
- # data-science (4)
- # datomic (65)
- # devcards (3)
- # dirac (91)
- # editors (7)
- # emacs (9)
- # hoplon (1)
- # jobs (5)
- # jobs-discuss (10)
- # juxt (2)
- # keechma (7)
- # ldnclj (31)
- # leiningen (3)
- # off-topic (22)
- # om (129)
- # om-next (1)
- # onyx (6)
- # proton (15)
- # protorepl (2)
- # re-frame (49)
- # reagent (13)
- # remote-jobs (1)
- # ring-swagger (2)
- # yada (19)
I was fiddling with replumb when I notice something: if I require a namespace, say foo.bar.baz
and before I had already required bar.core
both in cljs.user
(require 'foo.bar.baz)
triggers load-fn
on bar.core
again here
Loading dependencies for cljs.user
Loading foo.bar.baz namespace
<dump of foo.bar.baz>
Loading dependencies for cljs.user
Processing :use-macros for cljs.user
Processing :require-macros for cljs.user
Loading bar.core macros namespace ;; <- again?
...
...
is this the expected behavior or I am doing something wrong? it looks like it does it when (get-in state [:cljs.analyzer/namespaces 'cljs.user :require-macros])
returns bar.core
imho if I have already loaded bar.core
I should not reload it again, but I may be missing some good reason for doing this way