This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-30
Channels
- # announcements (8)
- # babashka (102)
- # beginners (312)
- # calva (9)
- # clj-kondo (9)
- # cljfx (7)
- # clojure (126)
- # clojure-europe (52)
- # clojure-nl (2)
- # clojure-norway (2)
- # clojure-spec (5)
- # clojure-uk (4)
- # clojurescript (13)
- # conjure (5)
- # cursive (5)
- # datalog (18)
- # datomic (8)
- # emacs (1)
- # events (3)
- # fulcro (16)
- # graphql (2)
- # gratitude (1)
- # helix (16)
- # inf-clojure (17)
- # introduce-yourself (9)
- # java (11)
- # lambdaisland (3)
- # leiningen (3)
- # lsp (8)
- # malli (3)
- # membrane (7)
- # missionary (26)
- # nextjournal (1)
- # off-topic (19)
- # pathom (3)
- # polylith (13)
- # portal (16)
- # reagent (39)
- # reitit (2)
- # releases (23)
- # remote-jobs (1)
- # shadow-cljs (40)
- # specter (3)
- # sql (12)
- # tools-deps (8)
- # tree-sitter (1)
- # vim (3)
- # web-security (6)
- # xtdb (16)
Sometimes I find the best place to put fn specs as metadata on de fn, like tests
(defn a
{:spec (s/fspec ...)}
[]
...)
is this something being considered for spec2? technically you can already do this, is there tooling around using specs on metadata?there are a lot of tradeoffs (var meta is evaluated in particular) and yes there are some things being considered here
👍 3
@alexmiller have you peeked at the survey responses? Does it help justify prioritisation/investment in v2 spec?
I have, although I didn't really need the survey to tell me people are interested in spec :)
🙂 7
I imagine checking the survey to confirm that people want spec2 is rather like checking a thermometer to confirm that lava is, indeed, hot