On Monday, October 2, 2017 at 12:30:57 PM UTC-5, Leon Grapenthin wrote: > > I second this from my experience, using spec quite extensively since its > release. > > We already had some invalid data passing silently because of this. It can > easily happen if you have a typo in the spec. > > Also we never experienced benefits from being able to not spec keys > required in s/keys. It appears to be a pretty obsolete feature, making > vulnerabilities more likely. >
It is more common to experience the negative effects of restricting key sets as you evolve through versions, and in fact we have experienced on virtually every consulting project we'd done including spec at Cognitect. So I do not think it is at all obsolete. -- 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.
