Ruby Issue Tracking System

08/03/2013

07:59 PM Ruby Feature #8723: Array.any? predicate returns true for empty array.

=========
"Do you agree at least that you initial proposal with assigning false to [].all?{...} was unreasonable?" --alexeymuranov
Well yes, I wanted it to return any false'y value, actually. Including nil. Sorry for not making it ... nurettin (Nurettin Onur TUGCU)

03:40 PM Ruby Feature #8723: Array.any? predicate returns true for empty array.

I find I need to address all the questions
=============
"If enum is empty, there is in fact *none* element which could not satisfy the predicate. " -- Eregon
none element which could not satisfy, you could interpret this as "a... nurettin (Nurettin Onur TUGCU)

08/02/2013

09:42 PM Ruby Feature #8723: Array.any? predicate returns true for empty array.

Yes, I meant for .all? (wasn't able to edit) and the behavior is correct according to docs, and incorrect according to my interpretation of sets. (can a predicate be true when you have empty set?) nurettin (Nurettin Onur TUGCU)

08:38 PM Ruby Feature #8723 (Rejected): Array.any? predicate returns true for empty array.

Are all your children redheaded?
Would this be true if you have no children?
I have no children, therefore none of my children are redheaded.
Therefore
[].any?{ true } == true makes no sense.
Expected behavior:
[].any?{ true } == ... nurettin (Nurettin Onur TUGCU)