Clojurians Log v2
lsp
transduuuuce it! 😃
Lol sorry, I don't have anything to contribute. I don't know about the internals of clojure-lsp nor clj-kondo. Is it possible to summarize the problem?
@raf clojure-lsp can sometimes (when indexing a new project) consume a lot of memory. We’d like to get that in control without sacrificing too much of the speed.
Right. And memory is consumed by clj-kondo needing stuff in memory for analysis? What do classpaths have to do with it?
Can't wait to have find-references for keywords work. E.g. I want to have the cursor on :refer and then get a list of all occurrences. Should work now with current clj-kondo analysis
@snoe I'm adding support for keywords, but I realized clj-kondo don't recognize :refer or :as in ns form as keywords
the rest seems to work pretty well
oh yeah, actually I wasn't after :refer in ns, but :refer in normal functions, for sci interpreter code
so that should work well
oh got it 😅
we can probably leave the ns form out for now, since it's not common that people want to find those keywords I think
agree
Just configured lsp for another subproject in the same mono-repo which has a slightly different way of building the classpath. Winning!
Oh, I missed that on clj-kondo, I though it was not available yet l
Nice, I can work on it soon
Was missing the like mad just an hour ago here. Drooling now. 😃
I Imagine de keywords analysis should increase a lot the analysis size right @borkdude?
Did you test it how much increased? Just a little concerned about the performance
Also, is there any opt-in flag for that? I lost the PR/commit that added that
We added integration tests to clojure-lsp :clojure-lsp: CI using babashka :babashka:🎉 (Ignore the next release, since I need to test the Github Actions running during graalvm build 😅)
I mentioned in the lsp issue. raised, it's commented out in the analysis/README.md in kondo. I think to turn it on you pass :analysis {:keywords true}
thanks