Begin/rescue/end blocks in Ruby - Time & Space Complexity

Time Complexity: Begin/rescue/end blocks

O(n)

Understanding Time Complexity

When we use begin/rescue/end blocks in Ruby, we want to know how the time to run the code changes as the input grows.

We ask: How much extra time does handling errors add when the input size changes?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

begin
  numbers = [1, 2, 3, 4, 5]
  total = 0
  numbers.each do |num|
    total += 10 / num
  end
rescue ZeroDivisionError
  puts "Cannot divide by zero!"
end
    

This code sums 10 divided by each number in an array, and handles division by zero errors if they occur.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each number in the array with each.
• How many times: Once for every element in the array (n times).

How Execution Grows With Input

As the array gets bigger, the number of divisions and additions grows in a straight line.

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

Pattern observation: The work grows evenly as the input grows; doubling input doubles work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the code grows in direct proportion to the number of items in the array.

Common Mistake

[X] Wrong: "The rescue block makes the whole code run slower for every item in the array."

[OK] Correct: The rescue block only runs if an error happens. If no error occurs, it does not slow down the loop itself.

Interview Connect

Understanding how error handling affects time helps you write clear and efficient code, a skill valued in real projects and interviews.

Self-Check

"What if the rescue block handled errors inside the loop instead of outside? How would the time complexity change?"

Practice

1. What is the purpose of the begin/rescue/end block in Ruby?

easy

A. To declare variables

B. To create a loop that repeats code

C. To define a new method

D. To handle errors and prevent the program from crashing

Solution

1. Step 1: Understand the role of begin block

   The begin block contains code that might cause an error.

2. Step 2: Understand the role of rescue block

   The rescue block catches errors and handles them so the program doesn't crash.

3. Final Answer:

   To handle errors and prevent the program from crashing -> Option D

4. Quick Check:

   begin/rescue = error handling [OK]

Hint: Remember: begin/rescue is for catching errors safely [OK]

Common Mistakes:

• Thinking begin/rescue creates loops
• Confusing rescue with method definition
• Using begin/rescue to declare variables

2. Which of the following is the correct syntax to handle exceptions using begin/rescue/end in Ruby?

easy

A. begin
risky_code
rescue
handle_error
end

B. try {
risky_code
} catch {
handle_error
}

C. if error then
handle_error
end

D. begin:
risky_code
except:
handle_error

Solution

1. Step 1: Identify Ruby syntax for error handling

   Ruby uses begin, rescue, and end keywords for exceptions.

2. Step 2: Compare options with Ruby syntax

   begin risky_code rescue handle_error end matches Ruby syntax exactly; others use syntax from other languages or incorrect keywords.

3. Final Answer:

   begin\n risky_code\nrescue\n handle_error\nend -> Option A

4. Quick Check:

   Ruby error handling = begin/rescue/end [OK]

Hint: Look for Ruby keywords: begin, rescue, end [OK]

Common Mistakes:

• Using try/catch like other languages
• Using if/else for error handling
• Mixing Python or JavaScript syntax

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

begin
  puts 10 / 0
rescue ZeroDivisionError
  puts "Cannot divide by zero"
end

medium

A. Cannot divide by zero

B. 0

C. 10

D. ZeroDivisionError

Solution

1. Step 1: Identify the error in the code

   The code tries to divide 10 by 0, which raises a ZeroDivisionError.

2. Step 2: Understand the rescue block

   The rescue block catches ZeroDivisionError and prints "Cannot divide by zero" instead of crashing.

3. Final Answer:

   Cannot divide by zero -> Option A

4. Quick Check:

   ZeroDivisionError caught = message printed [OK]

Hint: Divide by zero triggers rescue message [OK]

Common Mistakes:

• Expecting program to crash
• Thinking it prints 0 or 10
• Confusing error name with output

4. Find the error in this Ruby code snippet:

begin
  puts 5 + "3"
rescue
  puts "Error caught"
end

medium

A. The begin block should be replaced with try

B. The rescue block is missing the error type

C. You cannot add a number and a string directly

D. The code will run without errors

Solution

1. Step 1: Analyze the operation inside begin block

   Adding 5 (number) and "3" (string) causes a TypeError in Ruby.

2. Step 2: Check error handling

   The rescue block catches any error and prints "Error caught"; the error is due to incompatible types.

3. Final Answer:

   You cannot add a number and a string directly -> Option C

4. Quick Check:

   Type mismatch causes error caught [OK]

Hint: Check data types before adding values [OK]

Common Mistakes:

• Thinking rescue needs error type always
• Assuming code runs without error
• Confusing begin with try

5. How can you modify this code to handle multiple specific errors separately?

begin
  # risky code
rescue
  puts "An error occurred"
end

hard

A. Use if statements inside begin block

B. Use multiple rescue clauses with specific error classes

C. Replace rescue with else to catch errors

D. Put all code inside rescue block

Solution

1. Step 1: Understand handling multiple errors

   Ruby allows multiple rescue clauses to catch different error types separately.

2. Step 2: Apply multiple rescue clauses

   Write rescue clauses like rescue ZeroDivisionError and rescue IOError to handle errors distinctly.

3. Final Answer:

   Use multiple rescue clauses with specific error classes -> Option B

4. Quick Check:

   Multiple rescue = specific error handling [OK]

Hint: Use separate rescue for each error type [OK]

Common Mistakes:

• Using else instead of rescue
• Trying to catch errors with if statements
• Putting code inside rescue block