Add reduction `none()` as syntactic sugar in place of `!any()`



none() would work as follows:

none([false, false, true, false]) => false
none([false, false, false, false]) => true


!any is the same length as none and already works…


IMHO none would be much more clear when reading code… but I agree we can also live with !any.


Agreed – it’d give use the full set: any, all, and finally none.


Easy fix where you want to use it:

const none = !any