This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-11-21
Channels
- # announcements (1)
- # beginners (20)
- # biff (5)
- # calva (43)
- # cider (5)
- # clj-commons (7)
- # clj-kondo (11)
- # clojure (58)
- # clojure-brasil (1)
- # clojure-denmark (1)
- # clojure-europe (27)
- # clojure-nl (1)
- # clojure-norway (13)
- # clojure-uk (2)
- # clojurescript (71)
- # data-science (32)
- # datalevin (6)
- # datomic (19)
- # emacs (1)
- # gratitude (3)
- # honeysql (8)
- # hoplon (15)
- # hyperfiddle (3)
- # introduce-yourself (1)
- # lsp (19)
- # malli (4)
- # nbb (7)
- # other-lisps (5)
- # practicalli (1)
- # re-frame (14)
- # releases (1)
- # ring-swagger (1)
- # squint (118)
- # xtdb (9)
- # yada (2)
I checked the docs and issues and don't see a linter that I could use to detect (known) lazy-sequence-producing functions.
Usecase: it's idiomatic and easy to use the 2 (or more) arities of functions like map
and filter
, however, in a codebase that doesn't need to be lazy most of the time, I'd discourage their uses and would recommend the eager ...v
versions or - even better - transducers. The :discouraged-var
linter could be an option, however in most cases I'd want to discourage only specific arities.
Is there a way to do this currently, and if not, would it be in line with clj-kondo's goals to add a linter like this?