Any?, all?, none? predicates in Ruby - Step-by-Step Execution

Concept Flow - Any?, all?, none? predicates

Start with collection

↓

Check each element with predicate

↓

Any?

↓

True if any

↓

Return boolean

The program checks each element in a collection against a condition and returns true or false based on any, all, or none matching.

Execution Sample

Ruby

numbers = [1, 2, 3, 4]
puts numbers.any? { |n| n > 3 }
puts numbers.all? { |n| n > 0 }
puts numbers.none? { |n| n > 0 }

This code checks if any number is greater than 3, if all numbers are greater than 0, and if none are greater than 0.

Execution Table

Step	Method	Element	Predicate Result	Overall Result So Far
1	any?	1	false	false
2	any?	2	false	false
3	any?	3	false	false
4	any?	4	true	true (stop checking)
5	all?	1	true	true
6	all?	2	true	true
7	all?	3	true	true
8	all?	4	true	true
9	none?	1	true	false (stop checking)

💡 any? stops at element 4 because predicate is true; all? checks all elements; none? stops at element 1 because predicate is true

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	Final
any_result	nil	false	false	false	true	true
all_result	nil	true	true	true	true	true
none_result	nil	false	false	false	false	false

Key Moments - 3 Insights

Why does any? stop checking after finding a true predicate?

any? returns true as soon as one element satisfies the condition, so it stops early to save time (see row 4 in execution_table).

Why does all? check every element even if some are true?

all? must confirm every element meets the condition, so it only returns true if all are true (rows 5-8).

Why does none? stop checking after finding a true predicate?

none? returns false as soon as one element satisfies the condition, so it stops early (row 9).

Visual Quiz - 3 Questions

Look at the execution_table, what is the overall result of any? after checking element 3?

A true

B nil

C false

D error

💡 Hint

Check the 'any?' rows for elements 1 to 3 in the execution_table.

At which step does none? stop checking elements?

A Step 4

B Step 1

C Step 9

D It never stops early

💡 Hint

Look at the none? row in the execution_table and see when it stops.

If the array was empty, what would all? return?

A true

B false

C nil

D error

💡 Hint

Recall that all? returns true for empty collections by definition.

Concept Snapshot

any? checks if any element matches a condition and returns true immediately if found.
all? checks if all elements match a condition and returns false immediately if any fail.
none? checks if no elements match a condition and returns false immediately if any match.
These methods return boolean values and stop checking early when possible.
Use with a block that defines the condition to test each element.

Full Transcript

This lesson shows how Ruby's any?, all?, and none? methods work by checking elements in a collection against a condition. any? returns true if at least one element meets the condition and stops checking further. all? returns true only if every element meets the condition, so it checks all elements unless one fails early. none? returns true if no elements meet the condition and stops checking as soon as one does. The execution table traces each step and shows when the methods stop checking. The variable tracker shows how the results change after each element is checked. Key moments clarify why these methods stop early or check all elements. The quiz tests understanding of these behaviors. This helps beginners see how these predicates work step-by-step.