This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-16
Channels
- # announcements (7)
- # asami (31)
- # aws (9)
- # babashka (29)
- # bangalore-clj (8)
- # beginners (153)
- # calva (4)
- # cider (21)
- # clj-kondo (29)
- # clojure (78)
- # clojure-australia (2)
- # clojure-dev (63)
- # clojure-europe (22)
- # clojure-italy (7)
- # clojure-nl (3)
- # clojure-norway (4)
- # clojure-uk (25)
- # core-async (1)
- # cursive (24)
- # datomic (33)
- # emacs (15)
- # events (2)
- # fulcro (4)
- # girouette (1)
- # google-cloud (2)
- # graphql (14)
- # honeysql (15)
- # instaparse (1)
- # jobs (2)
- # jobs-discuss (2)
- # meander (18)
- # off-topic (100)
- # pathom (48)
- # pedestal (2)
- # polylith (5)
- # practicalli (4)
- # reveal (8)
- # shadow-cljs (3)
- # spacemacs (12)
- # sql (23)
- # tools-deps (1)
- # uncomplicate (1)
- # vim (21)
- # xtdb (19)
Made an (unedited, improvised) video on how we (at work) solve our deps.edn monorepo issues with a babashka script. https://youtu.be/PIwKYJh3r-Y
There is an issue for this: https://github.com/borkdude/edamame/issues/76
Iâm writing a small Clojure primer and had just mentioned âfunction literals canât be nestedâ, then evaluated my example for it. (Which to my surprise wasnât marked by the linter.) Only, I was using a babashka REPL. đ
They are quite unnecessary, though, I agree. Iâm mainly mentioning them as part of mentioning the dispatch character, and also so that you will recognize them when reading Clojure code.
We could have an optional linter for disallowing fn literals, but I'm not sure if I would go so far as to use it myself