This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-20
Channels
- # announcements (1)
- # beginners (65)
- # calva (16)
- # cider (44)
- # clara (16)
- # clojure (84)
- # clojure-dev (48)
- # clojure-europe (5)
- # clojure-finland (4)
- # clojure-houston (1)
- # clojure-italy (19)
- # clojure-nl (27)
- # clojure-russia (6)
- # clojure-spec (37)
- # clojure-uk (123)
- # clojured (11)
- # clojurescript (21)
- # datomic (40)
- # duct (4)
- # emacs (6)
- # figwheel (4)
- # figwheel-main (5)
- # fulcro (34)
- # jackdaw (8)
- # juxt (117)
- # kaocha (3)
- # klipse (1)
- # leiningen (33)
- # luminus (2)
- # nyc (3)
- # off-topic (29)
- # om (1)
- # pedestal (7)
- # planck (4)
- # re-frame (27)
- # reagent (8)
- # reitit (5)
- # rum (2)
- # shadow-cljs (428)
- # spacemacs (5)
- # tools-deps (15)
- # yada (6)
Hmmm... I've tried to understand what's going on the with the eval
/`load-string` namespace thing but it's beyond my understanding. When I look at the code, it looks to me like planck.core/eval
delegates to cljs.core/eval
which itself delegates to cljs.core/*eval*
with the intention that *eval*
will be bound at runtime. The thing is that I can't see anywhere where this runtime binding happens.
I've been looking into an experiment that might lead to a solution https://github.com/planck-repl/planck/commit/1be2eab8bce95a0f1439ee5317fa47ff45176487