Frozen objects in Ruby - Time & Space Complexity

Time Complexity: Frozen objects

O(n)

Understanding Time Complexity

When working with frozen objects in Ruby, it's important to understand how checking if an object is frozen affects performance.

We want to know how the time to check freezing grows as the program runs.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

array = ["apple", "banana", "cherry"].map(&:freeze)

array.each do |item|
  puts item.frozen?
end
    

This code freezes each string in an array and then checks if each item is frozen.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each item in the array to check if it is frozen.
• How many times: Once for each item in the array (n times).

How Execution Grows With Input

Each item is checked once, so the total work grows directly with the number of items.

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

Pattern observation: The work increases evenly as the list gets bigger.

Final Time Complexity

Time Complexity: O(n)

This means the time to check frozen status grows in a straight line with the number of items.

Common Mistake

[X] Wrong: "Checking if an object is frozen takes a long time because it inspects the whole object deeply."

[OK] Correct: Checking frozen status is a simple flag check and does not depend on object size.

Interview Connect

Understanding how simple property checks scale helps you reason about performance in real code, making you confident in explaining your choices.

Self-Check

"What if we froze a nested array inside each item and checked frozen? How would the time complexity change?"

Practice

1. What does the freeze method do to an object in Ruby?

easy

A. Makes the object mutable

B. Deletes the object from memory

C. Duplicates the object

D. Prevents any modifications to the object

Solution

1. Step 1: Understand the purpose of freeze

   The freeze method is used to make an object immutable, meaning it cannot be changed after freezing.

2. Step 2: Identify the effect on the object

   Once frozen, any attempt to modify the object will raise an error, so it prevents modifications.

3. Final Answer:

   Prevents any modifications to the object -> Option D

4. Quick Check:

   freeze makes object immutable = Prevents modifications [OK]

Hint: Freeze means no changes allowed to the object [OK]

Common Mistakes:

• Thinking freeze deletes the object
• Confusing freeze with duplication
• Believing freeze makes object mutable

2. Which of the following is the correct way to freeze a string object str in Ruby?

easy

A. str.freeze()

B. freeze str

C. str.freeze = true

D. freeze(str)

Solution

1. Step 1: Recall Ruby method call syntax

   In Ruby, methods are called on objects using dot notation, e.g., object.method.

2. Step 2: Identify the correct freeze syntax

   The correct way to freeze an object is by calling freeze on it: str.freeze(). The other options are invalid syntax.

3. Final Answer:

   str.freeze() -> Option A

4. Quick Check:

   Method call syntax = str.freeze() [OK]

Hint: Use dot notation to call freeze: object.freeze() [OK]

Common Mistakes:

• Using freeze as a standalone keyword
• Assigning freeze as a property
• Calling freeze like a function without dot

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

arr = [1, 2, 3]
arr.freeze
arr << 4
puts arr.inspect

medium

A. RuntimeError: can't modify frozen Array

B. [1, 2, 3, 4]

C. [1, 2, 3]

D. SyntaxError

Solution

1. Step 1: Understand freezing the array

   The array arr is frozen with arr.freeze, so it cannot be changed.

2. Step 2: Analyze the modification attempt

   The code tries to add an element with arr << 4, which modifies the array. Since it's frozen, this raises a runtime error.

3. Final Answer:

   RuntimeError: can't modify frozen Array -> Option A

4. Quick Check:

   Modifying frozen object = RuntimeError [OK]

Hint: Modifying frozen objects causes runtime errors [OK]

Common Mistakes:

• Expecting the array to change
• Thinking freeze allows modifications
• Confusing runtime error with syntax error

4. Identify the error in this Ruby code snippet:

name = "Alice"
name.freeze
name[0] = 'M'
puts name

medium

A. No error, output is "Mlice"

B. RuntimeError: can't modify frozen String

C. SyntaxError due to invalid assignment

D. TypeError: wrong type of argument

Solution

1. Step 1: Recognize string freezing

   The string name is frozen, so it cannot be changed after name.freeze.

2. Step 2: Understand the attempted modification

   Trying to change the first character with name[0] = 'M' modifies the string, which is forbidden and raises a runtime error.

3. Final Answer:

   RuntimeError: can't modify frozen String -> Option B

4. Quick Check:

   Changing frozen string = RuntimeError [OK]

Hint: Changing frozen strings causes runtime errors [OK]

Common Mistakes:

• Assuming strings can be changed after freeze
• Confusing syntax error with runtime error
• Ignoring freeze effect on string elements

5. Given this Ruby code, what will be the output?

hash = {a: [1, 2], b: [3, 4]}
hash.freeze
hash[:a] << 5
puts hash[:a].inspect

What does this tell us about freezing objects?

hard

A. RuntimeError: can't modify frozen Hash

B. [1, 2] - freeze prevents any changes including nested objects

C. [1, 2, 5] - freeze prevents changing the hash keys but not the objects inside

D. SyntaxError due to invalid hash modification

Solution

1. Step 1: Understand freezing the hash

   The hash object is frozen, so its structure (keys and values) cannot be changed directly.

2. Step 2: Analyze modification of nested array

   The value for key :a is an array, which is not frozen. Modifying this array with << 5 is allowed.

3. Step 3: Observe the output

   The array now contains [1, 2, 5], showing that freezing the hash does not freeze nested objects.

4. Final Answer:

   [1, 2, 5] - freeze prevents changing the hash keys but not the objects inside -> Option C

5. Quick Check:

   Freeze is shallow = nested objects can change [OK]

Hint: Freeze is shallow; nested objects stay mutable unless frozen [OK]

Common Mistakes:

• Assuming freeze affects nested objects
• Expecting runtime error on nested modification
• Confusing hash freezing with deep freeze