> The goal is to add the macro to orchestra, as a tool to help encourage > spec'ing all functions.
That would be great. My macro for now was also not supporting all defn cases yet. And it automatically instruments the fn with orchestra. So if orchestra had a more complete one defacto, I wouldn't need one. For performance, I've been thinking that caching validation (with some configurable cache bounds), or having sample based validation, so validating only a percentage of calls, and maybe even having the sampling rate controlled by execution time metrics, or cpu metrics or call rates, etc. would be interesting possibilities. So in prod, you could tweek the validation to only get as much of it as you can afford. -- 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.
