This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-03
Channels
- # announcements (11)
- # aws (1)
- # beginners (57)
- # calva (14)
- # cider (22)
- # clara (23)
- # cljdoc (21)
- # cljs-dev (14)
- # clojure (76)
- # clojure-austin (3)
- # clojure-europe (32)
- # clojure-finland (1)
- # clojure-gamedev (5)
- # clojure-italy (3)
- # clojure-nl (17)
- # clojure-poland (4)
- # clojure-spec (23)
- # clojure-uk (29)
- # clojurescript (72)
- # cursive (6)
- # data-science (4)
- # datomic (2)
- # dirac (10)
- # duct (3)
- # emacs (1)
- # figwheel-main (10)
- # fulcro (86)
- # jackdaw (5)
- # juxt (2)
- # kaocha (2)
- # leiningen (16)
- # off-topic (47)
- # pathom (46)
- # protorepl (2)
- # reagent (4)
- # reitit (14)
- # ring-swagger (5)
- # shadow-cljs (43)
- # spacemacs (13)
- # sql (13)
- # tools-deps (6)
Had an interesting back-and-forth with Dan Abramov of the React team about function names, munging and stack traces: https://github.com/facebook/react/issues/15259
I wonder if something could be done about this in the ClojureScript compiler? Certainly better looking stack traces would lift all boats but it seems like impossible to do if the function name has to be a valid JS identifier.
I don't really know a lot about how source maps work, but AFAICT stack traces in Chrome sometimes use them?
I will check with them what the support for source maps is. Just wanted to clarify since I’m a little bit clueless about compilation and munging etc.
@orestis FYI, dirac tries to give you better names in devtools and stacktraces: https://box.binaryage.com/dirac-non-trivial-beautified-stack-trace.png it uses code from cljs-devtools https://github.com/binaryage/cljs-devtools/blob/master/src/lib/devtools/munging.cljs