This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-02
Channels
- # announcements (3)
- # asami (29)
- # babashka (62)
- # beginners (131)
- # biff (7)
- # calva (31)
- # cider (5)
- # clerk (14)
- # clj-kondo (3)
- # cljsrn (12)
- # clojars (18)
- # clojure (72)
- # clojure-austin (17)
- # clojure-dev (6)
- # clojure-europe (31)
- # clojure-indonesia (1)
- # clojure-nl (1)
- # clojure-norway (18)
- # clojure-sweden (11)
- # clojure-uk (6)
- # clr (47)
- # conjure (42)
- # cursive (88)
- # datalevin (2)
- # datomic (25)
- # emacs (42)
- # exercism (1)
- # fulcro (10)
- # funcool (8)
- # gratitude (2)
- # honeysql (16)
- # introduce-yourself (5)
- # jobs-discuss (26)
- # leiningen (5)
- # lsp (31)
- # malli (21)
- # matcher-combinators (14)
- # missionary (2)
- # nbb (1)
- # off-topic (40)
- # pathom (38)
- # portal (2)
- # re-frame (7)
- # reagent (18)
- # reitit (1)
- # releases (5)
- # shadow-cljs (62)
- # sql (12)
- # testing (4)
- # xtdb (37)
I'm getting odd behavior from the relatively-new :unused-value
. I've got a macro used like
(mt/with-temp-env-var-value [not-a-real-binding (name (:some-key defaults))]
;; body...
)
that has [:hooks :macroexpand]
rules that turn it into
(defmacro with-temp-env-var-value [bindings & body]
`(do
~@(map second (partition-all 2 bindings))
~@body))
it's flagging the (name (:some-key defaults))
as "unused value". if I replace it with 7
, (:some-key defaults)
, or even (-> defaults :some-key name)
, it doesn't complain.
that last especially makes it feel like a bug in the linter, since that should itself produce identical expanded code to the original.