On Jun 10, 2017 11:57 AM, "Mark" <markaddle...@gmail.com> wrote:

I'm embarking on a new project and I think spec can be a central component
not just to the developer-users of the system but to my end-users as well.
I'm thinking of providing something like a graphical mechanism to describe
specs in EDN to bring spec goodness to user created data pipelines.  My
only concern is the global registry.  Quickly browsing spec alpha-17's
code, it appears the that global registry is an implementation detail of
the map spec and, perhaps, others.

Would it make sense to provide an additional arity for the conform*,
unform* and explain* fns which take a user-supplied registry?


what about using a global config var like *spec-registry* to control which
registry gets used?

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to