Fork me on GitHub
#cursive
<
2020-05-04
>
Jordan Robinson08:05:05

Hey all, since the last update 1.9.1-2020.1, (or maybe due to 2020.1 as they updated at the same time for me) it seems like I can't put breakpoints in certain files. Instead I get the message: Line 15 in foo$eval15927 (bar)  No executable code found at line 15 in class bar.foo$thing  Suspend: all I can still put breakpoints successfully in some files, and hit them, but not others. I'm unsure if this is related to https://github.com/cursive-ide/cursive/issues/2345 or if I'm missing something, so are there any troubleshooting steps I can take on this one? I've already invalidated caches and restarted from intellij but happy to try any ideas

Jordan Robinson15:05:39

I think I've pinned this one down, it looks like the debugger won't load the code if the namespace contains a _ instead of a -. Obviously this was a mistake in the code, so easily fixable in my case, but not the easiest to pin down 😅

Roman Liutikov09:05:09

Could be interesting if Cursive could leverage ClojureScript's type inference to display types inline in the code https://github.com/cursive-ide/cursive/issues/2365

cfleming09:05:34

Yes, I’ve planned that for a while for CLJS, but haven’t done anything on it yet. It’s hard to reuse the analysis environment, I’ll probably reuse a fair amount of the code that’s used for the Clojure analysis.

cfleming09:05:10

Doing this right for CLJS required upgrading Cursive’s knowledge of JS in general first though, which will also help node_modules imports etc.

Roman Liutikov09:05:08

Do you plan to propagate JS deps info into ClojureScript to improve inspections?

cfleming10:05:43

And JS deps type info, assuming I can get the information out of the Closure parser.

folcon13:05:29

How do people use the debugger? You need to run the repl in debug mode right? Isn’t that really slow?

imre14:05:28

just out of curiosity, Alex, are you a Cursive user yourself? For some reason I was under the impression all of Cognitect use emacs

imre14:05:47

I noticed you are active in this channel

Alex Miller (Clojure team)14:05:27

people use a variety of editors at Cognitect

imre14:05:22

Cheers, good to know there's someone in the core team walking in our shoes 🙂

folcon16:05:11

Hmm, I used to have the impression that it was, I’ll have to give that a whirl then, do you tend to do development in a debug repl then?

Alex Miller (Clojure team)16:05:34

sometimes. if I'm not really doing any interop, I don't usually bother because that's really the only time I use the debugger

4
kenny17:05:06

I asked Colin about this a while ago. He said that he always starts his REPL up in debug mode. I have started doing the same. It's nice to have the debug features readily available without needing to do a REPL restart. The only hiccup I've had is when working with large lazy seqs (and I mean decently large - to the tune of a 20-30gb csv file). Debug mode disables locals clearing which, depending on your code, can cause a lot of memory usage when working with large lazy seqs.

folcon20:05:48

Hmm, ok, that’s a downside, but it sounds like it’s well worth giving it a shot =)…

kenny21:05:43

Unless you're working with tons of data, you won't have any issues.