I have found, as an application evolves, some extra data is required which comes from elsewhere.
For example, I have an application where data is read from a network socket, transformed and stored. For auditing, I later decided it was useful to capture the remote address from the socket right at the start, and finally to log it. With restrictive specs, I would have had to re-spec all the intermediate functions. As it was, they didn't know or need to know about the extra key/value in the map, just pass it along. On puzzler's database example, I would have thought that restricting the keys that go into the DB should not be the job of spec (since functions may not be instrumented anyway), but the job of the 'core logic'. Maybe I am misunderstanding though. -- 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.
