Frozen objects in Ruby - Step-by-Step Execution

Concept Flow - Frozen objects

Create object

↓

Freeze object

↓

Try to modify object?

Yes→Error: can't modify frozen object

No↓

Use object as is

↓

End

An object is created and then frozen to prevent changes. Any attempt to modify it causes an error.

Execution Sample

Ruby

str = "hello"
str.freeze
str << " world"

Create a string, freeze it, then try to add more text (which causes an error).

Execution Table

Step	Action	Object State	Result/Output
1	Create string str = "hello"	str = "hello" (not frozen)	No output
2	Call str.freeze	str = "hello" (frozen)	No output
3	Try str << " world"	str frozen	Error: can't modify frozen String

💡 Execution stops at step 3 due to error when modifying frozen object

Variable Tracker

Variable	Start	After freeze	After modification attempt
str	"hello" (not frozen)	"hello" (frozen)	"hello" (frozen, unchanged)

Key Moments - 2 Insights

Why does modifying the string after freezing cause an error?

Because freezing marks the object as unchangeable. The execution_table step 3 shows the error when trying to modify a frozen object.

Does freezing change the content of the object?

No, freezing only prevents changes. The variable_tracker shows the string content stays "hello" before and after freezing.

Visual Quiz - 3 Questions

Look at the execution_table step 2, what is the state of the string object?

A Not frozen, can be changed

B Frozen, cannot be changed

C Deleted from memory

D Empty string

💡 Hint

Check the 'Object State' column at step 2 in execution_table

At which step does the program stop due to an error?

A Step 3

B Step 2

C Step 1

D No error occurs

💡 Hint

Look at the 'Result/Output' column in execution_table for error messages

If we remove the freeze call, what would happen at step 3?

A Error: can't modify frozen String

B String becomes empty

C String changes to "hello world"

D Program crashes immediately

💡 Hint

Consider variable_tracker and what freezing does to the object

Concept Snapshot

In Ruby, calling freeze on an object makes it immutable.
Any attempt to change a frozen object raises an error.
Use freeze to protect objects from accidental modification.
Frozen objects keep their content but cannot be altered.
Trying to modify frozen objects stops the program with an error.

Full Transcript

This example shows how Ruby's freeze method works. First, a string object is created with the value "hello". Then, the freeze method is called on this string, marking it as frozen. When the program tries to add more text to the frozen string using <<, Ruby raises an error because frozen objects cannot be changed. The variable tracker confirms the string content stays the same before and after freezing. This prevents accidental changes to important data. The execution stops at the modification attempt due to the error. Removing freeze would allow the string to change normally.

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