This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-17
Channels
- # announcements (1)
- # aws (7)
- # babashka (5)
- # calva (56)
- # cider (13)
- # clj-commons (1)
- # clj-kondo (12)
- # clj-yaml (35)
- # clojure (84)
- # clojure-europe (93)
- # clojure-sg (2)
- # clojure-uk (1)
- # clojurescript (10)
- # conjure (37)
- # core-typed (1)
- # cursive (31)
- # duct (1)
- # figwheel-main (4)
- # fulcro (2)
- # holy-lambda (2)
- # humbleui (3)
- # membrane (118)
- # off-topic (46)
- # pathom (8)
- # podcasts-discuss (5)
- # releases (2)
- # rewrite-clj (13)
- # sci (27)
- # shadow-cljs (17)
- # tools-deps (12)
I'm writing a new linter to find unused values... and yikes, I found one in clj-kondo... One of the category: how could this ever have worked

The unfortunate answer is that since it hasn’t worked, now this same behavior is probably scattered across the relevant code paths making the whole thing a bit more complex… 🙂
Can’t wait to turn this on in my production code. How does it know what is or is not a pure function?
Does clj-kondo do anything different than rewrite-clj when parsing?
Are the differences documented anywhere?
Hmm… there is some mention of the whitespace thing in https://github.com/clj-kondo/clj-kondo/blob/1e4d23fd03659342cfd4b6ccc7eded59fc68ff3e/doc/hooks.md.
It might also deal with namespaced maps differently. I think rewrite-clj got inlined (then customized) from rewrite-clj v0.
Ah thank you. I’m working with rewrite-clj for that pattern matching library i mentioned the other day but realized once I started that there are probably differences