This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-12-19
Channels
- # adventofcode (18)
- # announcements (1)
- # babashka (153)
- # beginners (73)
- # bristol-clojurians (4)
- # calva (1)
- # cider (6)
- # clj-kondo (38)
- # clojure (154)
- # clojure-dev (12)
- # clojure-europe (7)
- # clojure-finland (11)
- # clojure-nl (70)
- # clojure-spec (13)
- # clojure-uk (101)
- # clojuredesign-podcast (2)
- # clojurescript (15)
- # core-async (30)
- # cryogen (1)
- # cursive (5)
- # devops (1)
- # duct (4)
- # figwheel-main (1)
- # fulcro (19)
- # jobs (12)
- # kaocha (17)
- # luminus (2)
- # malli (8)
- # music (5)
- # nrepl (13)
- # off-topic (20)
- # overtone (3)
- # re-frame (7)
- # reagent (38)
- # shadow-cljs (13)
- # specter (3)
- # tools-deps (6)
- # vim (7)
ace-link now supports cider inspector 🙂 https://github.com/abo-abo/ace-link/pull/59 I find it really handy for navigating directly to an inspectable object
I think I've spotted a minor bug in the CIDER step debugger. When trying to instrument for debugging a function which contains a method call imported with the (old!) import-static
library (https://clojure.github.io/clojure-contrib/import-static-api.html), cider-nrepl throws a StackOverflow error.
This is because the way in which this library works. For example, if I say:
(import-static java.lang.Integer parseInt)
A parseInt
macro is created in my current namespace, which expands like this:
(parseInt "3") ==> (. java.lang.Integer (parseInt "3"))
Trying to evaluate this with the debugger crashes with a SatckOverflow.
I suspect cider is not correctly interpreting the dot special form, and recursively macroexpands the (parseInt) static call until it crashes. Note that this code compiles just fine, it's just when cider tries to instrument it that it fails because the macroexpand phase is not done correctly.
Do you think I should I report this as an issue? Or is support for something like this not considered?