[Solved] Why does merge return a new hash instead of modifying the original hash? — Ans: To keep the original hash unchanged and allow safe merging | Ruby

Ruby - Hashes

Why does merge return a new hash instead of modifying the original hash?

ATo keep the original hash unchanged and allow safe merging

BBecause Ruby hashes are immutable

CTo improve performance by avoiding changes

DBecause update method is deprecated

Step-by-Step Solution

Solution:

Step 1: Understand immutability concept in merge
merge returns a new hash to avoid changing the original, preserving data safety.
Step 2: Eliminate incorrect reasons
Ruby hashes are mutable, update is not deprecated, and performance is not the main reason.
Final Answer:
To keep the original hash unchanged and allow safe merging -> Option A
Quick Check:
merge returns new hash to preserve original [OK]

Quick Trick: merge returns new hash to avoid side effects [OK]

Common Mistakes:

MISTAKES

Master "Hashes" in Ruby

9 interactive learning modes - each teaches the same concept differently

More Ruby Quizzes

Why does merge return a new hash instead of modifying the original hash?