This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-07
Channels
- # announcements (10)
- # babashka (11)
- # beginners (69)
- # calva (1)
- # cider (2)
- # clj-kondo (35)
- # cljdoc (48)
- # cljs-dev (3)
- # clojure (60)
- # clojurescript (10)
- # community-development (6)
- # cursive (4)
- # datahike (1)
- # datalog (33)
- # deps-new (2)
- # depstar (8)
- # docker (24)
- # fulcro (1)
- # graphql (4)
- # honeysql (5)
- # java (2)
- # leiningen (2)
- # missionary (3)
- # off-topic (104)
- # pedestal (8)
- # polylith (18)
- # portkey (3)
- # reagent (7)
- # reveal (1)
- # rewrite-clj (4)
- # shadow-cljs (19)
- # specter (3)
- # tools-deps (2)
I was using the cider debugger, via C-u C-c C-c when evaluating a form. I noticed that on the clojure.core.match/match forms the debugger struggles to show the exact place of the evaluation. How are macros handled in the cider debugger? Could one add explicit support for clojure.match?
relating compiled code to the macros that generated it is kind of a usual problem for tools to have... e.g. clj-kondo or tools.analyzer can show slightly incorrect line/column info when macros are involved for a debugger, I reckon that the debugger can't instrument something that was executed already at macroexpansion time? don't quote me on that though :)