This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-14
Channels
- # ai (3)
- # babashka (45)
- # beginners (81)
- # biff (26)
- # calva (10)
- # cider (5)
- # clj-kondo (55)
- # cljfx (6)
- # clojure (125)
- # clojure-berlin (1)
- # clojure-europe (37)
- # clojure-italy (7)
- # clojure-nl (3)
- # clojure-norway (79)
- # clojure-uk (1)
- # clojurescript (63)
- # clojutre (1)
- # conjure (5)
- # cursive (37)
- # data-science (1)
- # datalevin (4)
- # datomic (28)
- # eastwood (6)
- # fulcro (26)
- # graphql (20)
- # honeysql (6)
- # humbleui (4)
- # jobs-discuss (5)
- # kaocha (1)
- # leiningen (8)
- # missionary (5)
- # nbb (4)
- # observability (3)
- # off-topic (7)
- # pathom (8)
- # podcasts-discuss (1)
- # rewrite-clj (18)
- # ring (6)
- # sci (23)
- # scittle (9)
- # shadow-cljs (49)
- # squint (10)
- # testing (11)
- # xtdb (17)
Minor but handy release https://github.com/jonase/eastwood/blob/v1.3.0/changes.md#changes-from-125-to-130
I thought there was already a linter some years ago that could warn about uses of assoc!
and other transient operations, if you called them but discarded their return value. It has been years since I looked at it, but I recall at least considering implementing something like that. Perhaps it bit-rotted since then.
Perhaps the :unused-ret-vals
linter did that at some point in the past?
@U0CMVHBL2 there's a fair chance that assoc!
once was defined like that. var-info.edn has had its churn/'bugs'.
Now with unit tests it's more difficult that the intent gets lost in the way
In any case, cool that you added the capability back in if it was not there in the latest version of Eastwood.