Jan RychterFeb 26

clj-kondo success story: over the course of several months I managed to get from 1360 warnings and 179 errors to 72 warnings and 8 errors (yes, it's a large code base).

I found a good amount of dead code, made lots of small improvements/refactorings and found around 10 actual bugs.

[The remaining warnings are spurious and can't really be fixed without modifying clj-kondo]

If you write Clojure, I highly recommend clj-kondo.

Thank you @borkdude for all your work on this excellent tool! 🙏

Show thread(λ. borkdude)Feb 26
@jrychter Thanks for the huge compliment. Are the remaining warnings the ones you talked about in Github? Those are fixable by introducing per-dialect branches for ignoring unused locals etc. If it's anything else, please let me know.
Show threadJan RychterFeb 26
@borkdude Most of them, yes. I have one other namespace-related clj/cljs issue that *might* also be the same problem, and a few errors that I simply do not understand and that I need to form into issues (things like "error: Insufficient input.", "Unresolved var: uuid/v4 where uuid/v4 very much exists", "error: Expected: deref, received: nil.", and clj-kondo insisting on a different function arity in some cases).
Show thread(λ. borkdude)Feb 26
@jrychter Feel free to discuss in the clj-kondo channel on Clojurians or Github issues. Might very well be bugs in clj-kondo.
Show threadJan Rychter
@borkdude Thank you! I will, and we'll see, perhaps I can help with bizarre cases 🙂
Feb 26 at 7:57pmWeb