Boolean collection functions (anyTrue, not, ...) fail on empty collections

[piotrszul]

not(), anyTrue(), allTrue(), anyFalse(), allFalse() fail on explicit empty collections while they should produce a result.

(Existence exclusions)

Details

java.lang.IllegalArgumentException: argument type mismatch

• Functions.attrempty.not() [** empty coll with not() is empty coll]
• Functions.nothing.not() [** not nothing is empty coll]

Details

java.lang.IllegalArgumentException: argument type mismatch

• Functions.attrempty.allTrue() [** allTrue for empty coll is true]
• Functions.nothing.allTrue() [** allTrue for non exists coll is true]

Details

java.lang.IllegalArgumentException: argument type mismatch

• Functions.attrempty.anyTrue() [** anyTrue for empty coll is false]
• Functions.nothing.anyTrue() [** anyTrue for non-exists coll is false]

Details

java.lang.IllegalArgumentException: argument type mismatch

• Functions.attrempty.allFalse() [** allFalse for empty coll is true]
• Functions.nothing.allFalse() [** allFalse for non-exists coll is true]

Details

java.lang.IllegalArgumentException: argument type mismatch

• Functions.attrempty.anyFalse() [** anyFalse for empty coll is false]
• Functions.nothing.anyFalse() [** anyFalse for non-exists coll is false]

[johngrimes]

These functions should only ever return true or false.

[piotrszul]

The functions do return true or false for empty boolean collections. For empty collections of other types including the empty literal {} they fail, because of type mismatch. This is most likely the same as for in version 7.0.0.

[johngrimes]

@piotrszul I have just confirmed that this is still a problem (for not) in the v8 branch.