This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-08-18
Channels
- # announcements (22)
- # asami (7)
- # babashka (43)
- # beginners (68)
- # biff (2)
- # calva (10)
- # clj-kondo (7)
- # cljdoc (29)
- # clojure (41)
- # clojure-austin (1)
- # clojure-brasil (2)
- # clojure-europe (25)
- # clojure-gamedev (3)
- # clojure-nl (2)
- # clojure-norway (9)
- # clojure-uk (31)
- # clojurescript (3)
- # community-development (7)
- # cursive (3)
- # data-science (4)
- # datomic (17)
- # emacs (30)
- # honeysql (10)
- # hyperfiddle (39)
- # introduce-yourself (1)
- # jobs-discuss (5)
- # kaocha (1)
- # lsp (11)
- # malli (12)
- # pathom (18)
- # pedestal (3)
- # proletarian (2)
- # quil (11)
- # rdf (46)
- # reitit (8)
- # releases (2)
- # shadow-cljs (34)
- # sql (3)
- # squint (10)
- # tools-deps (24)
- # xtdb (10)
What do folks think of a linter for non-double-wrapped anonymous function forms in thread-first constructs? I expect it's so rare that anyone wants to thread a value into the name slot of a function that it can safely be a lint error (maybe optional). Got the idea from a question in #beginners just now. E.g.
(-> foo (fn [x] (bar x)))
I'd wager no one has ever done this on purpose.🎯 4
i'd use that
As in, you'd use the linter, or you'd use that syntax purposefully (I assume the former 😅 )
it took me a while to get used to (-> ... (#(...)))
fwiw, I made an issue and linked a PR, here: https://github.com/clj-kondo/clj-kondo/issues/2159
👍 4