Nothing specific but for the same reason you'd want to use 'and' in other scenarios. You want the short-circuit behavior if certain criteria are met.
Only in this case you just want a function that does it instead. One contrived example coming to mind: (every-fn iterative-has-next? get-next) Of course there are likely better ways to deal with iterators in Clojure. It is just a contrived example. The basic idea is that the 'every-fn' is checking certain properties of the args first prior to calling the fn that relies on those properties being a certain way. I'm not saying this is a common scenario I have. I think I'm Java interop cases these sort of things come up a bit more often for me though. My overall point is that it is more convenient/useful in more scenarios to return the value instead of 'true'. That is what makes it convenient and useful to use 'or' and 'and' and 'some-fn' in non-predicate ways. 'every-pred' is an outlier. -- 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.
