Usage: (every? pred coll)The usage of every? is very straightforward, but a quick REPL session is always nice to verify our assumptions.
Returns true if (pred x) is logical true for every x in coll, else false.
Clojure 1.2.0As expected, every? works well when you know exactly what predicate you need to use.
user=> (every? nil? [nil nil nil])
user=> (every? nil? [nil 1])
Yesterday, I was working on some code that included checking for nil - similar to the example below.
user=> (def front 1)This code works perfectly if you have the individual elements "front" and "back", but as the code evolved I ended up representing "front" and "back" simply as a list of elements. Changing to a list required a way to verify that each entry in the list was not nil.
user=> (def back 2)
user=> (when (and front back) [front back])
I was 99% sure that "and" was a macro; therefore, combining it with apply wasn't an option. A quick REPL reference verified my suspicion.
user=> (def legs [front back])Several other options came to mind, an anonymous function that checked for (not (nil? %)), map the values to (not (nil? %)) and use every? with true?; however, because of Clojure's truthiness the identity function is really all you need. The following REPL session shows how identity works perfectly as our predicate for this example.
user=> (when (apply and legs) legs)
java.lang.Exception: Can't take value of a macro: #'clojure.core/and (NO_SOURCE_FILE:8)
(when (every? identity legs) legs)For a few more looks at behavior, here's a few examples that include nil and false.
user=> (every? identity [1 2 3 4])As you can see, using identity will cause every? to fail if any element is falsey (nil or false). In my case the elements are integers or nil, so this works perfectly; however, it's worth noting so you don't see unexpected results if booleans ever end up in your list.
user=> (every? identity [1 2 nil 4])
user=> (every? identity [1 false 4])