This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-05
Channels
- # all-the-channels (1)
- # announcements (3)
- # asami (13)
- # beginners (227)
- # calva (2)
- # chlorine-clover (8)
- # cider (7)
- # clj-kondo (4)
- # cljs-dev (21)
- # cljsrn (8)
- # clojure (64)
- # clojure-europe (39)
- # clojure-france (2)
- # clojure-italy (3)
- # clojure-losangeles (1)
- # clojure-nl (20)
- # clojure-uk (8)
- # clojurescript (24)
- # conjure (12)
- # datalog (9)
- # datomic (24)
- # emacs (8)
- # figwheel-main (1)
- # fulcro (15)
- # jobs-discuss (1)
- # malli (5)
- # meander (3)
- # off-topic (26)
- # re-frame (15)
- # reagent (10)
- # reitit (1)
- # reveal (1)
- # sci (15)
- # shadow-cljs (25)
- # spacemacs (7)
- # sql (3)
- # xtdb (1)
@kevin.van.rooijen I'll take a look. Can you maybe write a repro of your issue in a Github issue?
@kevin.van.rooijen I'm not sure what's the right answer here. ^:foo
is expanded into {:foo true}
. Should the :postprocess
function only see {:foo true}
or {:tag FooBar}
(in case of type hints)?
@kevin.van.rooijen This function is applied to the metadata value after postprocess has been applied: https://github.com/clojure/tools.reader/blob/528e01ef4f4f6b8750b3f9a50c13d6561f254f6d/src/main/cljs/cljs/tools/reader/impl/utils.cljs#L64
Hmm, that doesn't work, since the value produced by desugar isn't going through the reader
@kevin.van.rooijen The problem here is that the value produced by desugar is not read from source code, so by definition it has no location metadata
@kevin.van.rooijen I now pushed a solution to the branch desugar-postprocess
both forms now get your {{:value :foo} true}
as meta. I do need to look into a performance regression that this may incur