This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-05
Channels
- # announcements (14)
- # aws (7)
- # babashka (28)
- # beginners (16)
- # calva (2)
- # cider (1)
- # clj-commons (8)
- # clj-kondo (29)
- # clojure (213)
- # clojure-europe (39)
- # clojure-losangeles (2)
- # clojure-norway (9)
- # clojure-spec (2)
- # clojurescript (11)
- # community-development (1)
- # conjure (2)
- # cursive (6)
- # datalevin (2)
- # datomic (8)
- # emacs (29)
- # events (1)
- # fulcro (22)
- # graalvm (14)
- # improve-getting-started (1)
- # jobs (1)
- # lambdaisland (5)
- # leiningen (4)
- # lsp (7)
- # malli (13)
- # meander (11)
- # membrane (13)
- # off-topic (23)
- # polylith (9)
- # re-frame (4)
- # reagent (7)
- # reitit (6)
- # releases (2)
- # sql (58)
- # testing (8)
- # tools-deps (18)
- # web-security (2)
Hello! When I use the debugger, i have to hit “step into” up 3 times to get to the next line of code.
I also cant set breakpoints in let bindings.
I also sometimes see that the debugger go to the else form of if and then goes back to the “then” form.
I dont see any of these issues in github. Does anyone else have these issues?
As Alex mentions, this is to do with how Clojure compiles to bytecode. I’m planning to discuss this with JetBrains to see if I can work around it, but I haven’t done so yet.
I’ve filed this issue as a catch-all for these sorts of problems: https://github.com/cursive-ide/cursive/issues/2739. I’d like to get some simple repro cases in there I can take to JetBrains, I’ll try to come up with some next week but if anyone else has any drop them either here or over on the issue.
A lot of this has to do with how Clojure code is translated into bytecode with source mappings
I have definitely seen some of those issues