Fork me on GitHub
#clojure-spec
<
2018-05-10
>
triss10:05:52

is there a quick way to flush the slipnet library thing?

devn17:05:36

What's the rationale for having a spec registry?

devn17:05:39

The Data spec registration and Function spec registration sections in https://clojure.org/about/spec get at it

devn17:05:54

guess I was wondering if you'd add any additional color

Alex Miller (Clojure team)17:05:24

not a lot to add beyond that

Alex Miller (Clojure team)17:05:47

there was a desire to not keep shoving stuff into var meta

devn17:05:50

@alexmiller I wondered "Vars themselves are a kind of registry, no?"

Alex Miller (Clojure team)17:05:07

with good names, we are not limited to a single “var” registry

Alex Miller (Clojure team)17:05:56

if you use vars, you need namespaces to hold them

Alex Miller (Clojure team)17:05:23

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

Alex Miller (Clojure team)17:05:03

Rich has some future ideas on managing names and aliases independently from namespaces

devn17:05:29

this pleases me greatly

devn17:05:25

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

Alex Miller (Clojure team)17:05:19

yeah, that’s a hack. we have aims to do better.

Oliver George23:05:40

This hurts most in clojurescript. Do you think it will be supported in the new approach?

Alex Miller (Clojure team)00:05:58

Probably but I don’t know what it is yet :)

Oliver George02:05:47

Can't say fairer than that. I look forward to specs becoming less verbose and quicker to write.

devn17:05:24

there's also the potential for the "oops, someone clobbered a spec name and didn't know about it" situation