This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-12-06
Channels
- # admin-announcements (7)
- # beginners (37)
- # boot (36)
- # cider (8)
- # cljs-dev (16)
- # clojure (155)
- # clojure-hamburg (1)
- # clojure-russia (2)
- # clojurecup (21)
- # clojurescript (69)
- # clojurex (12)
- # core-async (2)
- # datavis (3)
- # datomic (5)
- # devcards (4)
- # events (2)
- # hoplon (15)
- # lein-figwheel (45)
- # off-topic (22)
- # om (77)
- # re-frame (8)
- # reagent (7)
- # slack-help (1)
I'm investigating the cacheability of macro namespaces when using the cache facilities provided by cljs.js
.
@mfikes: I'm investigating how should cljs files be recompiled if the macro files that produced them where changed. I guess it's macro Sunday
@bensu: That's cool. Sounds like a dependency tree would be part of the solution. Hmm. What if one clj file depends on another…
@mfikes: yes, that is the hairy part! I'll start handling the first order case, and then see how much effort is needed to build a clojure dep graph on the side.
@bensu: I'll keep an eye on your stuff and see if it is applicable to bootstrap as well (perhaps with mild relaxation on how it works?)
@dnolen: if a cljs file should be recompiled because one of its required macros changed, the macro file should also be loaded
so, if I have a new fn that returns macros-changed? => true
, then I should load the macros and recompile the file.
the problem is that it seems that macros-changed?
should be added as a condition inside cljs.compiler/requires-compilation?
but the side-effects should be called outside.