This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-01
Channels
- # announcements (7)
- # babashka (41)
- # beginners (117)
- # cider (3)
- # clj-kondo (145)
- # cljdoc (25)
- # cljs-dev (19)
- # clojure (197)
- # clojure-dev (14)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-spec (11)
- # clojure-uk (21)
- # clojuredesign-podcast (5)
- # clojurescript (29)
- # code-reviews (4)
- # cursive (87)
- # data-science (11)
- # datomic (29)
- # duct (2)
- # emacs (10)
- # graalvm (1)
- # lumo (13)
- # malli (2)
- # nrepl (5)
- # off-topic (25)
- # onyx (1)
- # pathom (6)
- # reagent (20)
- # reitit (4)
- # rewrite-clj (7)
- # shadow-cljs (114)
- # spacemacs (16)
@lee np - re: comments from you and borkdude at #calva-dev > I did recently fix a bug where I was using the wrong clojure reader in one spot. > that can surely make a difference. using tools.reader/... vs tools.reader.edn/... can make things go bad with graalvm are there any relevant commits i might take a look at?
ah, may be it's this one: https://github.com/lread/rewrite-cljs-playground/commit/630ac1074a87185e997f4250d661235aa3d78b82
@lee oh, that might have done the trick -- i'll need to verify in detail, but at least the build seems to have succeeded.
atm, my take is that at least the build issue i was experiencing may be solved by using:
[clojure.tools.reader.edn :as edn]
instead of:
[clojure.tools.reader :as edn]
in parser/keyword.cljc
since you've already made that change, may be the particular situation i was encountering is taken care of.
hopefully, i can exhibit something that's clearer soon.