Why methods always return a value in Ruby - Performance Analysis

Time Complexity: Why methods always return a value in Ruby

O(n)

Understanding Time Complexity

When we look at Ruby methods, they always give back a result. Understanding how this affects the time it takes to run helps us write better code.

We want to see how the work done inside a method grows as the input changes.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

def sum_array(numbers)
  total = 0
  numbers.each do |num|
    total += num
  end
  total
end

This method adds up all numbers in an array and returns the total sum.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each number in the array.
• How many times: Once for every number in the input array.

How Execution Grows With Input

As the array gets bigger, the method does more additions, one for each number.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: The work grows directly with the number of items. Double the items, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows in a straight line with the input size.

Common Mistake

[X] Wrong: "The method returns instantly because it just returns a value."

[OK] Correct: Even though a method returns a value, it still does all the work inside first, which takes time depending on input size.

Interview Connect

Knowing how method return values relate to the work done inside helps you explain code efficiency clearly and confidently.

Self-Check

"What if we changed the method to return the sum of only the first half of the array? How would the time complexity change?"

Practice

1. Why do Ruby methods always return a value even if there is no explicit return statement?

easy

A. Because Ruby methods must always have a return statement.

B. Because Ruby methods return the first line's value automatically.

C. Because Ruby methods return nil by default if no value is given.

D. Because Ruby automatically returns the value of the last executed line in the method.

Solution

1. Step 1: Understand Ruby method return behavior

   Ruby methods do not require an explicit return statement to send back a value.

2. Step 2: Identify what value is returned

   The value of the last executed line inside the method is automatically returned.

3. Final Answer:

   Because Ruby automatically returns the value of the last executed line in the method. -> Option D

4. Quick Check:

   Last line value returned [OK]

Hint: Remember: last line in method is returned automatically [OK]

Common Mistakes:

• Thinking a return statement is always needed
• Believing methods return nil if no return is used
• Assuming the first line's value is returned

2. Which of the following is the correct way to define a Ruby method that returns the sum of two numbers without using an explicit return?

easy

A. def add(a, b)
return a + b
end

B. def add(a, b)
a + b
end

C. def add(a, b)
puts a + b
end

D. def add(a, b)
a + b; nil
end

Solution

1. Step 1: Check method syntax without explicit return

   def add(a, b) a + b end defines a method where the last line is a + b, which will be returned automatically.

2. Step 2: Compare other options

   def add(a, b) return a + b end uses explicit return (also correct but not asked). def add(a, b) puts a + b end prints the sum but returns nil. def add(a, b) a + b; nil end returns nil explicitly.

3. Final Answer:

   def add(a, b) a + b end -> Option B

4. Quick Check:

   Last line expression returned [OK]

Hint: Last expression in method is returned without return keyword [OK]

Common Mistakes:

• Using puts instead of returning value
• Adding explicit nil at the end
• Confusing printing with returning

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

def greet(name)
  "Hello, #{name}!"
  42
end

puts greet("Alice")

medium

A. "Hello, Alice!"

B. nil

C. 42

D. SyntaxError

Solution

1. Step 1: Analyze method body lines

   The method has two lines: first creates a string but does not return it explicitly; second line is the number 42.

2. Step 2: Identify returned value

   Ruby returns the last evaluated expression, which is 42.

3. Final Answer:

   42 -> Option C

4. Quick Check:

   Last line value returned = 42 [OK]

Hint: Method returns last line value, not earlier lines [OK]

Common Mistakes:

• Assuming first string line is returned
• Confusing puts output with return value
• Expecting nil because no explicit return

4. The following Ruby method is intended to return the string "Done", but it returns nil instead. What is the error?

def finish
  puts "Done"
end

result = finish
puts result.inspect

medium

A. The method uses puts which returns nil, so method returns nil.

B. The method is missing an explicit return statement.

C. The method should use print instead of puts.

D. The method name is reserved and cannot be used.

Solution

1. Step 1: Understand what puts returns

   puts prints to screen but returns nil.

2. Step 2: Identify method return value

   Since puts "Done" is the last line, method returns nil.

3. Final Answer:

   The method uses puts which returns nil, so method returns nil. -> Option A

4. Quick Check:

   puts returns nil [OK]

Hint: puts returns nil, so method returns nil if last line is puts [OK]

Common Mistakes:

• Thinking puts returns the printed string
• Believing explicit return is always needed
• Confusing print and puts behavior

5. You want a Ruby method to return the first non-nil value from two expressions. Which method definition correctly uses Ruby's automatic return to achieve this?

def first_non_nil(a, b)
  # fill in
end

hard

A. def first_non_nil(a, b)
a || b
end

B. def first_non_nil(a, b)
return a if a
return b
end

C. def first_non_nil(a, b)
puts a || b
end

D. def first_non_nil(a, b)
a
b
end

Solution

1. Step 1: Understand the goal

   We want the method to return the first non-nil value between a and b.

2. Step 2: Check each option's return value

   def first_non_nil(a, b) a || b end returns a || b which evaluates to first non-nil value automatically. def first_non_nil(a, b) return a if a return b end uses explicit returns but is longer. def first_non_nil(a, b) puts a || b end prints but returns nil. def first_non_nil(a, b) a b end returns b always because last line is b.

3. Final Answer:

   def first_non_nil(a, b) a || b end -> Option A

4. Quick Check:

   Last expression returns first non-nil [OK]

Hint: Use last line expression to return desired value without return [OK]

Common Mistakes:

• Using puts instead of returning value
• Writing multiple return statements unnecessarily
• Returning wrong line's value