Why functional patterns complement OOP in Ruby - Performance Analysis

Time Complexity: Why functional patterns complement OOP

O(n)

Understanding Time Complexity

We want to see how combining functional patterns with object-oriented programming affects how long code takes to run.

Specifically, we ask: How does adding functional style change the work done as input grows?

Scenario Under Consideration

Analyze the time complexity of the following Ruby code mixing OOP and functional style.

class Calculator
  def initialize(numbers)
    @numbers = numbers
  end

  def sum_squares
    @numbers.map { |n| n * n }.reduce(0, :+)
  end
end

calc = Calculator.new([1, 2, 3, 4])
puts calc.sum_squares
    

This code defines a class holding numbers and uses functional methods to square and sum them.

Identify Repeating Operations

Look for loops or repeated work inside the code.

• Primary operation: The map method loops over each number to square it.
• Secondary operation: The reduce method loops again to add all squared numbers.
• How many times: Each method loops once over all numbers, so two passes total.

How Execution Grows With Input

As the list of numbers grows, the code does more work in two passes.

Input Size (n)	Approx. Operations
10	About 20 (10 for map + 10 for reduce)
100	About 200 (100 + 100)
1000	About 2000 (1000 + 1000)

Pattern observation: The work grows roughly twice as fast as the input size because of two passes.

Final Time Complexity

Time Complexity: O(n)

This means the time to finish grows directly in proportion to how many numbers we have.

Common Mistake

[X] Wrong: "Using two loops means the time complexity is squared, like O(n²)."

[OK] Correct: The loops run one after another, not inside each other, so their times add up, not multiply.

Interview Connect

Understanding how functional methods work inside classes helps you explain clear, readable code that scales well.

Self-Check

What if we combined the map and reduce into a single loop? How would the time complexity change?

Practice

1. Which of the following best explains why functional patterns complement Object-Oriented Programming (OOP) in Ruby?

easy

A. Functional patterns make Ruby code run faster by avoiding objects.

B. Functional patterns replace the need for classes and objects entirely.

C. OOP discourages the use of methods and focuses only on data.

D. Functional patterns create small, reusable methods without side effects, improving code clarity.

Solution

1. Step 1: Understand functional patterns in Ruby

   Functional patterns emphasize small, reusable methods that avoid changing data outside their scope (no side effects).

2. Step 2: Understand OOP's role

   OOP organizes code around objects that combine data and behavior, making programs easier to manage.

3. Final Answer:

   Functional patterns create small, reusable methods without side effects, improving code clarity. -> Option D

4. Quick Check:

   Functional patterns improve clarity by avoiding side effects [OK]

Hint: Functional = small, pure methods; OOP = objects with data [OK]

Common Mistakes:

• Thinking functional replaces OOP completely
• Believing OOP ignores methods
• Assuming functional always makes code faster

2. Which Ruby syntax correctly defines a pure function that doubles a number without changing any external state?

easy

A. def double(x); x * 2; end

B. def double(x); @value = x * 2; end

C. def double(x); puts x * 2; end

D. def double(x); x *= 2; nil; end

Solution

1. Step 1: Identify pure function characteristics

   A pure function returns a value based only on input and does not change external variables or produce side effects.

2. Step 2: Check each option

   def double(x); x * 2; end returns x * 2 without changing anything else. def double(x); @value = x * 2; end changes an instance variable (@value), so it has side effects. def double(x); puts x * 2; end prints output (side effect). def double(x); x *= 2; nil; end modifies x locally but returns nil, so it doesn't return the doubled value.

3. Final Answer:

   def double(x); x * 2; end -> Option A

4. Quick Check:

   Pure function returns value only [OK]

Hint: Pure functions return values without side effects [OK]

Common Mistakes:

• Using instance variables inside pure functions
• Printing inside functions instead of returning
• Not returning the computed value explicitly

3. What is the output of this Ruby code combining OOP and functional style?

class Calculator
  def initialize(value)
    @value = value
  end

  def double
    @value * 2
  end

  def apply(func)
    func.call(@value)
  end
end

calc = Calculator.new(5)
puts calc.double
puts calc.apply(->(x) { x + 3 })

medium

A. 10
8

B. 10
15

C. 5
8

D. Error: undefined method

Solution

1. Step 1: Understand the Calculator class methods

   The double method returns @value * 2, so for 5 it returns 10. The apply method calls the passed function with @value.

2. Step 2: Evaluate the output of puts statements

   calc.double prints 10. calc.apply calls the lambda adding 3 to 5, so prints 8.

3. Final Answer:

   10 8 -> Option A

4. Quick Check:

   double = 10, apply adds 3 = 8 [OK]

Hint: Remember lambdas called with .call and return values [OK]

Common Mistakes:

• Confusing lambda call syntax
• Expecting apply to modify @value
• Mixing up output values

4. Identify the error in this Ruby code that tries to combine functional and OOP styles:

class Counter
  def initialize
    @count = 0
  end

  def increment
    @count += 1
  end

  def apply(func)
    func(@count)
  end
end

counter = Counter.new
counter.increment
puts counter.apply(->(x) { x * 2 })

medium

A. Lambda syntax is incorrect

B. increment method should return @count

C. func should be called with .call, not func()

D. Instance variable @count is not initialized

Solution

1. Step 1: Check how func is used in apply method

   In Ruby, to call a lambda or Proc, you must use .call, not func().

2. Step 2: Identify the error

   func(@count) will cause a NoMethodError because func is a Proc object and needs .call.

3. Final Answer:

   func should be called with .call, not func() -> Option C

4. Quick Check:

   Call lambdas with .call [OK]

Hint: Use .call to invoke lambdas or Procs [OK]

Common Mistakes:

• Calling lambda like a normal method
• Forgetting to initialize instance variables
• Incorrect lambda syntax

5. You want to create a Ruby class that stores a list of numbers and provides a method to return a new list with each number doubled, without changing the original list. Which approach best combines functional patterns with OOP?

hard

A. Modify the original list inside the method by doubling each element in place.

B. Define a method that returns a new array using map without modifying the original list.

C. Store the doubled values in an instance variable and return it directly.

D. Use a global variable to hold the doubled list and update it inside the method.

Solution

1. Step 1: Understand the requirement

   The method should not change the original list but return a new list with doubled values.

2. Step 2: Evaluate options for functional and OOP style

   Using map returns a new array without side effects, fitting functional style. Modifying original data or using global variables breaks this principle.

3. Final Answer:

   Define a method that returns a new array using map without modifying the original list. -> Option B

4. Quick Check:

   Use map for new array, avoid side effects [OK]

Hint: Use map to transform arrays without changing originals [OK]

Common Mistakes:

• Modifying original array instead of returning new
• Using global variables for data storage
• Storing results in instance variables unnecessarily