This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-19
Channels
- # announcements (6)
- # aws (10)
- # beginners (73)
- # bristol-clojurians (2)
- # calva (9)
- # cider (25)
- # clj-kondo (7)
- # clojure (160)
- # clojure-dev (2)
- # clojure-europe (63)
- # clojure-italy (7)
- # clojure-nl (10)
- # clojure-uk (76)
- # clojuredesign-podcast (6)
- # clojurescript (63)
- # cursive (6)
- # data-science (3)
- # datomic (26)
- # duct (59)
- # emacs (1)
- # fulcro (12)
- # graalvm (17)
- # hoplon (23)
- # jobs-discuss (2)
- # kaocha (6)
- # meander (7)
- # off-topic (3)
- # pathom (2)
- # rdf (68)
- # re-frame (12)
- # reagent (20)
- # reitit (5)
- # ring (3)
- # ring-swagger (1)
- # shadow-cljs (14)
- # spacemacs (10)
- # sql (3)
- # tools-deps (30)
- # yada (9)
There is something wrong with the indexing on the latest intellij eap/beta. Im getting that low memory notification and the responsiveness grinds to a halt. Same project, same eap10 cursive on 2019.3.4 has no issue indexing a lot my jars in .m2 in about 10-15 seconds. Has anyone else noticed something similar? I can't even report any errors because I have to force kill the while IDE
I haven’t experienced this, or received any other reports of it. Does invalidating caches help?
I have recently upgraded 8ntelliJ and am also regularly getting indexing pauses, which I didn't before. I suspect it's IntelliJ, not Cursive
@cfleming have you ever thought about extending code suggestions from the connected repl? Sometimes a namespace would stuff like potemkin/import-vars
to define vars. Static analysis won't be able to resolve that but it would be helpful if the warnings could change to weak warnings when the vars are available at runtime.