This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-07
Channels
- # announcements (13)
- # atom-editor (3)
- # babashka (53)
- # beginners (28)
- # clojure (30)
- # clojure-australia (4)
- # clojure-europe (22)
- # clojure-germany (1)
- # clojure-italy (6)
- # clojure-nl (3)
- # clojure-norway (14)
- # clojure-spec (8)
- # clojure-uk (8)
- # clojurescript (19)
- # cursive (33)
- # datomic (4)
- # defnpodcast (6)
- # events (3)
- # fulcro (3)
- # graalvm (77)
- # jobs (2)
- # juxt (11)
- # podcasts-discuss (1)
- # reitit (1)
- # releases (2)
- # remote-jobs (2)
- # sci (1)
- # shadow-cljs (27)
- # sql (6)
- # testing (10)
- # tools-deps (36)
- # vim (4)
- # xtdb (15)
Having watched the 2018 talk on monads (Maybe Not) and appreciating the case made for place oriented programming using maps and spec, the question i have - Does this lead to design of most non-pure functions accepting and returning maps (almost) exclusively?
What makes you think that?
composing, avoiding imperative style, while still supporting error context
in Clojure 1.11, you can pass a trailing map to a function that takes kwargs, so kwarg style also accepts map invocation
positional args are a tradeoff - they make invocation easier by making the arg name implicit
but that also means they are fragile to positional changes, whereas maps / kwargs are not