Clojurians Log v2
dev-tooling
FYI - I've created #cider-development for discussions specific to CIDER's development, so we won't spam you here with topics that are not of general interested to everyone. (e.g. CIDER's release planning, etc)
I added a bookmark to cider-nrepl docs to this channel. (Since they are very hard to find using Google or similar means 😃 )
I've love Slack bookmarks and I use them a lot on the job.
In other news - we didn't get any issue reports for nREPL 1.2-beta2 so far, so I'll likely cut a new release later this week. As a reminder - it brings back the ability to interrupt code evaluation on Java 20+ and improves a lot the bencode performance.
I haven’t gotten around to implement this in Calva. But it all looks great to me and I don’t see any particular troubles with implementing support.
Yeah, it's really just a matter of loading the JVMTI agent, so it should be fairly simple for jack-in, and for the other use-cases it's basically an entry in the docs that users need to load it themselves.
E.g. something like https://docs.cider.mx/cider/basics/up_and_running.html#enabling-nrepl-jvmti-agent
> it brings back the ability to interrupt code evaluation on Java 20+ How did you implement this without Thread/stop being available?
Ah JVMTI I see
We considered another option as well (see https://github.com/nrepl/nrepl/issues/296#issuecomment-2098870752), but the JVMTI option seemed better overall.
Btw, @cfleming what is the Clojure version that Cursive targets these days?
I try to support pretty much anything gracefully. In practice things that most people are using (e.g. nREPL) have some minimum value, but I try to make sure that Cursive handles it all.
Interesting. nREPL targets Clojure 1.7, but if we get to a point where no tool supports it we might switch to targeting some newer Clojure. That's why I asked.
Sure, again it’s easier due to my policy of mostly doing things by static analysis and minimal eval-only use of the REPL. So it’s easier to maintain support for older versions. I actually don’t test older versions so it’s possible some 1.7 stuff might have crept in, but no-one has complained about it either.