clj-kondo

2025-07-15T00:20:36.843909Z

a number of clojure core functions have stated inputs and outputs but can also return nils (`keyword`, meta, etc). is that something clj-kondo should account for?

borkdude 2025-07-15T06:38:46.267069Z

Only if it’s observable in linting I would say

πŸ‘ 1
borkdude 2025-07-15T10:57:18.957639Z

keyword returning nil seems like accidental behavior to me

borkdude 2025-07-15T10:57:29.406959Z

meta on the other hand is legit behavior

borkdude 2025-07-15T10:58:11.243199Z

The docstring of meta also explicitly states that it returns nil in some cases, keyword states that is returns a keyword

πŸ‘ 1
ghadi 2025-07-15T16:00:38.370829Z

is there a linter that complains about inline #_ linter config?

2025-07-15T16:01:25.291739Z

there's one that checks if a given #_ linter config is unnecessary

ghadi 2025-07-15T16:01:32.548729Z

i hate seeing inline config

πŸ˜‚ 1
ghadi 2025-07-15T16:01:45.792929Z

like redundant?

2025-07-15T16:01:58.928499Z

like, it didn't catch any warnings

ghadi 2025-07-15T16:01:58.937839Z

config file and inline say the same thing

ghadi 2025-07-15T16:02:03.911739Z

oh

2025-07-15T16:02:37.066699Z

but there's nothing for rejecting all inline configs. it's an interesting request

dpsutton 2025-07-15T16:05:50.693599Z

could you disable it with an inline linter config? 🧠

πŸ˜‚ 4
borkdude 2025-07-15T16:14:25.813479Z

here's a linter:

! rg "#_:clj-kondo"; echo $?

2
❀️ 1
πŸ˜† 3