--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
So I was thinking of:
user=> (any? true? [false true false])trueuser=> (any? even? [1 2 3])true; touch "3"user=> (any? #(.exists %) [(file "1") (file "2") (file "3")])true
Some motivations- my main one is Java interop where use of non booleans would be weird
- similarly it is nicer for APIs to return booleans than a value that is kinda arbitrary and potentially non deterministic. I might recall Rich saying something like that..?
- the symmetry of `any` joining `not-any`, `every` and `not-every`.