Predicate methods (ending with ?) in Ruby - Time & Space Complexity

Time Complexity: Predicate methods (ending with ?)

O(n)

Understanding Time Complexity

We want to understand how long it takes for predicate methods to run as the input changes.

Specifically, we ask: how does the time grow when checking conditions with these methods?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

def all_even?(numbers)
  numbers.all? { |num| num.even? }
end

list = [2, 4, 6, 8, 10]
puts all_even?(list)

This code checks if all numbers in a list are even using a predicate method.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Iterating over each number in the list to check if it is even.
• How many times: Up to once per element, stopping early if a number is not even.

How Execution Grows With Input

As the list gets longer, the method checks more numbers, but it may stop early if a number is odd.

Input Size (n)	Approx. Operations
10	Up to 10 checks
100	Up to 100 checks
1000	Up to 1000 checks

Pattern observation: The number of checks grows roughly in direct proportion to the list size.

Final Time Complexity

Time Complexity: O(n)

This means the time to check grows linearly with the number of items in the list.

Common Mistake

[X] Wrong: "Predicate methods always run in constant time because they just check a condition."

[OK] Correct: Even though the check is simple, the method may need to look at every item in the list, so time grows with input size.

Interview Connect

Understanding how predicate methods scale helps you explain your code's efficiency clearly and confidently.

Self-Check

"What if we changed all? to any?? How would the time complexity change?"

Practice

1. What does a predicate method in Ruby always return?

easy

A. A string value

B. A boolean value (true or false)

C. An integer value

D. An array

Solution

1. Step 1: Understand predicate method purpose

   Predicate methods in Ruby are designed to answer yes/no questions about an object or data.

2. Step 2: Identify return type of predicate methods

   They always return true or false, which are boolean values.

3. Final Answer:

   A boolean value (true or false) -> Option B

4. Quick Check:

   Predicate methods return true/false [OK]

Hint: Predicate methods always answer yes/no questions [OK]

Common Mistakes:

• Thinking predicate methods return strings or numbers
• Confusing predicate methods with regular methods
• Ignoring the question mark at the end

2. Which of the following is the correct way to define a predicate method in Ruby?

easy

A. def valid?; true; end

B. def valid; true; end

C. def valid!; true; end

D. def valid: true; end

Solution

1. Step 1: Recognize predicate method naming

   Predicate methods must end with a question mark (?).

2. Step 2: Check method syntax

   def valid?; true; end defines a method named valid? correctly with def and end keywords.

3. Final Answer:

   def valid?; true; end -> Option A

4. Quick Check:

   Method name ends with ? and syntax is correct [OK]

Hint: Predicate methods end with ? and use def ... end [OK]

Common Mistakes:

• Omitting the question mark in method name
• Using invalid method name characters like ! or :
• Incorrect method definition syntax

3. What will be the output of this Ruby code?

def empty_string?(str)
  str.empty?
end

puts empty_string?("")
puts empty_string?("hello")

medium

A. false\ntrue

B. true\ntrue

C. true\nfalse

D. false\nfalse

Solution

1. Step 1: Understand the method behavior

   The method empty_string? calls str.empty? which returns true if str is an empty string.

2. Step 2: Evaluate the calls

   empty_string?("") returns true because "" is empty; empty_string?("hello") returns false because "hello" is not empty.

3. Final Answer:

   true\nfalse -> Option C

4. Quick Check:

   Empty string check returns true, non-empty returns false [OK]

Hint: empty? returns true only for empty strings [OK]

Common Mistakes:

• Assuming non-empty strings return true
• Confusing empty? with nil? method
• Ignoring the question mark in method names

4. Identify the error in this Ruby code:

def positive?(num)
  if num > 0
    true
  else
    false
  end
end

puts positive?("5")

medium

A. ArgumentError because "5" is a string, not a number

B. SyntaxError due to missing end

C. No error, outputs true

D. Returns nil instead of true/false

Solution

1. Step 1: Analyze method input and comparison

   The method compares num > 0, but "5" is a string, not a number.

2. Step 2: Understand Ruby type comparison

   Comparing string "5" with integer 0 causes an ArgumentError at runtime.

3. Final Answer:

   ArgumentError because "5" is a string, not a number -> Option A

4. Quick Check:

   Comparing string and integer causes ArgumentError [OK]

Hint: Check input types before numeric comparisons [OK]

Common Mistakes:

• Passing strings instead of numbers
• Assuming no error on mixed type comparisons
• Missing end keyword (not the case here)

5. You want to create a predicate method valid_name? that returns true only if a string is not empty and contains only letters. Which implementation is correct?

hard

A. def valid_name?(name)
name.nil? && name.match?(/[a-z]/)
end

B. def valid_name?(name)
name.empty? || name.match?(/\d+/)
end

C. def valid_name?(name)
name.length > 0 && name.include?(' ')
end

D. def valid_name?(name)
!name.empty? && name.match?(/^[a-zA-Z]+$/)
end

Solution

1. Step 1: Understand the requirements

   The method must return true only if the string is not empty and contains only letters.

2. Step 2: Evaluate each option

   def valid_name?(name) !name.empty? && name.match?(/^[a-zA-Z]+$/) end checks that name is not empty and matches only letters using regex /^[a-zA-Z]+$/. This meets the requirements.

3. Final Answer:

   def valid_name?(name) !name.empty? && name.match?(/^[a-zA-Z]+$/) end -> Option D

4. Quick Check:

   Not empty and only letters = valid_name? true [OK]

Hint: Use regex and empty? to validate strings in predicates [OK]

Common Mistakes:

• Using || instead of && for conditions
• Checking for digits instead of letters
• Ignoring empty string check