Initialize method as constructor in Ruby - Time & Space Complexity

Time Complexity: Initialize method as constructor

O(1)

Understanding Time Complexity

We want to understand how the time it takes to create an object changes as we add more data inside it.

How does the constructor method's work grow when given more information?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Person
  def initialize(name, hobbies)
    @name = name
    @hobbies = hobbies
  end
end

person = Person.new("Alice", ["reading", "swimming", "coding"])

This code creates a new Person object with a name and a list of hobbies.

Identify Repeating Operations

Look for any repeated work inside the constructor.

• Primary operation: Assigning the list of hobbies to an instance variable.
• How many times: The assignment happens once, but the list size can vary.

How Execution Grows With Input

The constructor sets the name and hobbies once each. The time to assign the hobbies depends on how many hobbies there are.

Input Size (n)	Approx. Operations
10 hobbies	About 1 assignment (the list reference)
100 hobbies	About 1 assignment (the list reference)
1000 hobbies	About 1 assignment (the list reference)

Pattern observation: The work grows directly with the number of hobbies given only if the constructor processes the list; otherwise, it is constant time.

Final Time Complexity

Time Complexity: O(1)

This means the time to create the object does not grow with the number of hobbies if it just assigns the list reference.

Common Mistake

[X] Wrong: "The constructor always takes the same time no matter what."

[OK] Correct: If the constructor copies or processes a list, the time depends on the list size, so it grows as the list grows.

Interview Connect

Understanding how constructors handle input size helps you explain object creation costs clearly and confidently in interviews.

Self-Check

"What if the constructor also loops through hobbies to print each one? How would the time complexity change?"

Practice

1. What is the purpose of the initialize method in a Ruby class?

easy

A. It sets up initial values for a new object automatically.

B. It deletes an object from memory.

C. It prints the object details to the screen.

D. It defines a class method.

Solution

1. Step 1: Understand the role of initialize

   The initialize method is called automatically when a new object is created.

2. Step 2: Recognize what initialize does

   It sets starting values for the object's instance variables, preparing the object for use.

3. Final Answer:

   It sets up initial values for a new object automatically. -> Option A

4. Quick Check:

   initialize sets starting values [OK]

Hint: Remember: initialize runs when you create a new object [OK]

Common Mistakes:

• Thinking initialize deletes objects
• Confusing initialize with printing methods
• Believing initialize defines class methods

2. Which of the following is the correct way to define an initialize method in Ruby?

easy

A. def initialize(name)
@name = name
end

B. def Initialize(name)
@name = name
end

C. initialize def(name)
@name = name
end

D. def init(name)
@name = name
end

Solution

1. Step 1: Check method naming conventions

   Ruby requires the constructor method to be named exactly initialize in lowercase.

2. Step 2: Verify method syntax

   def initialize(name) @name = name end correctly defines def initialize(name) and assigns the instance variable @name.

3. Final Answer:

   def initialize(name)\n @name = name\nend -> Option A

4. Quick Check:

   Method name must be initialize lowercase [OK]

Hint: Use lowercase 'initialize' exactly to define constructor [OK]

Common Mistakes:

• Capitalizing 'Initialize' instead of 'initialize'
• Using wrong method syntax order
• Naming method 'init' instead of 'initialize'

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

class Person
  def initialize(name)
    @name = name
  end
  def greet
    "Hello, #{@name}!"
  end
end

p = Person.new("Alice")
puts p.greet

medium

A. Hello, @name!

B. Hello, Alice!

C. Hello, !

D. Error: undefined method greet

Solution

1. Step 1: Understand object creation and initialization

   The Person.new("Alice") calls initialize with "Alice", setting @name to "Alice".

2. Step 2: Check the greet method output

   The greet method returns "Hello, #{@name}!" which becomes "Hello, Alice!" when printed.

3. Final Answer:

   Hello, Alice! -> Option B

4. Quick Check:

   Instance variable set in initialize used in greet [OK]

Hint: Instance variables set in initialize are accessible in other methods [OK]

Common Mistakes:

• Expecting '@name' to print literally
• Forgetting to call greet method
• Confusing instance variable scope

4. Identify the error in this Ruby class definition:

class Car
  def initialize(make, model)
    make = make
    model = model
  end
end

car = Car.new("Toyota", "Corolla")
puts car.make

medium

A. The initialize method should not have parameters.

B. The puts statement should be puts car.model

C. The class name should be lowercase.

D. Instance variables are not assigned; should use @make and @model.

Solution

1. Step 1: Check variable assignment in initialize

   The code assigns local variables make = make and model = model, which do nothing to the object.

2. Step 2: Correct usage of instance variables

   To store values in the object, it should assign @make = make and @model = model.

3. Final Answer:

   Instance variables are not assigned; should use @make and @model. -> Option D

4. Quick Check:

   Use @variable to store data in object [OK]

Hint: Use @ before variable to save it in the object [OK]

Common Mistakes:

• Assigning to local variables instead of instance variables
• Thinking parameters auto become instance variables
• Wrong class naming conventions

5. You want to create a Ruby class Book that stores title and author when a new book is created. Which code correctly uses initialize to do this and allows reading these values later?

hard

A. class Book
def initialize(title, author)
@title = title
@author = author
end
def title
title
end
end

B. class Book
def initialize(title, author)
title = title
author = author
end
end

C. class Book
attr_reader :title, :author
def initialize(title, author)
@title = title
@author = author
end
end

D. class Book
def initialize(title, author)
@title = title
@author = author
end
def get_title
@title
end
end

Solution

1. Step 1: Check instance variable assignment

   Three options assign @title = title and @author = author correctly in initialize.

2. Step 2: Verify how values are accessed

   class Book attr_reader :title, :author def initialize(title, author) @title = title @author = author end end uses attr_reader to create getter methods for both title and author, allowing easy access.

3. Step 3: Identify issues in other options

   class Book def initialize(title, author) title = title author = author end end does not assign instance variables, so values are lost. class Book def initialize(title, author) @title = title @author = author end def title title end end's title method returns local variable title which is undefined. class Book def initialize(title, author) @title = title @author = author end def get_title @title end end only provides a getter for title, not author.

4. Final Answer:

   class Book attr_reader :title, :author def initialize(title, author) @title = title @author = author end end -> Option C

5. Quick Check:

   Use attr_reader with instance variables for easy access [OK]

Hint: Use attr_reader to read instance variables easily [OK]

Common Mistakes:

• Not assigning instance variables in initialize
• Returning undefined local variables in getter methods
• Missing getter methods for instance variables