[Solved] Why does freezing an object in Ruby not guarantee deep immutability of nested objects? — Ans: Because freeze only prevents modifications to the object itself, not its nested... | Ruby

Ruby - Functional Patterns in Ruby

Why does freezing an object in Ruby not guarantee deep immutability of nested objects?

ABecause freeze converts nested objects to strings

BBecause freeze only prevents modifications to the object itself, not its nested objects

CBecause freeze only works on arrays and hashes

DBecause freeze automatically duplicates nested objects

Step-by-Step Solution

Solution:

Step 1: Understand shallow freeze
freeze makes the object immutable but does not affect nested objects inside it.
Step 2: Nested objects remain mutable
Nested arrays or hashes inside a frozen object can still be changed unless they are frozen separately.
Final Answer:
Because freeze only prevents modifications to the object itself, not its nested objects -> Option B
Quick Check:
freeze is shallow, nested objects stay mutable unless frozen [OK]

Quick Trick: freeze is shallow; freeze nested objects separately for deep immutability [OK]

Common Mistakes:

Master "Functional Patterns in Ruby" in Ruby

9 interactive learning modes - each teaches the same concept differently

More Ruby Quizzes

Why does freezing an object in Ruby not guarantee deep immutability of nested objects?