This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-10
Channels
- # beginners (35)
- # cider (165)
- # cljsrn (18)
- # clojars (1)
- # clojure (141)
- # clojure-greece (2)
- # clojure-italy (11)
- # clojure-nl (1)
- # clojure-spec (21)
- # clojure-uk (89)
- # clojurescript (56)
- # community-development (3)
- # cursive (3)
- # data-science (55)
- # datomic (13)
- # emacs (12)
- # fulcro (31)
- # graphql (6)
- # jobs-discuss (35)
- # lein-figwheel (10)
- # mount (2)
- # off-topic (3)
- # onyx (22)
- # parinfer (4)
- # portkey (7)
- # re-frame (29)
- # ring-swagger (4)
- # shadow-cljs (37)
- # specter (9)
- # sql (30)
- # tools-deps (15)
- # vim (2)
- # yada (17)
The Data spec registration and Function spec registration sections in https://clojure.org/about/spec get at it
not a lot to add beyond that
there was a desire to not keep shoving stuff into var meta
@alexmiller I wondered "Vars themselves are a kind of registry, no?"
with good names, we are not limited to a single “var” registry
if you use vars, you need namespaces to hold them
with a separate registry, it’s perfectly ok to make a spec named :a.b.c.d.e.f.g/foo without having a related namespace
Rich has some future ideas on managing names and aliases independently from namespaces
we have a spec aliases macro for calling alias
+ create-ns
that we use, and while it works, it doesn't have good mouth feel
yeah, that’s a hack. we have aims to do better.
This hurts most in clojurescript. Do you think it will be supported in the new approach?
Probably but I don’t know what it is yet :)
Can't say fairer than that. I look forward to specs becoming less verbose and quicker to write.