On 12 Jun 2017, at 20:41, Mark <markaddle...@gmail.com> wrote: > > I don't see how that limits it to dev use cases. Can you explain more why > > you say that? > > I understand (and completely agree with) the assumption of a global namespace > for spec names. The scope of that namespace is all Clojure developers. I > want a different scope: the users of my app. To continue on this thinking, > if my app was shared among different customers, each customer would have > their own namespace - their own registry.
What problem would be solved by each customer having his own registry? > Further, I suspect that the lifecycle for specs in my app's scope will be a > bit different than the Clojure developer scope. Specifically, I can see that > some customers will insist on retracting specs. What do you mean by retracting specs? And what problem would this solve? Alan -- 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.
