Symbol type and immutability in Ruby - Step-by-Step Execution

Concept Flow - Symbol type and immutability

Create Symbol :name

↓

Symbol stored in memory

↓

Use Symbol in code

↓

Symbol is immutable

↓

Reuse same Symbol object

↓

No new object created

Symbols are unique, immutable names stored once in memory and reused whenever referenced.

Execution Sample

Ruby

:name.object_id == :name.object_id
:name.to_s
name = :name
name = :other

This code shows that the same symbol has the same object id, symbols are immutable, and assigning symbols.

Execution Table

Step	Code	Action	Result/Output
1	:name.object_id	Get object id of :name symbol	e.g. 123456 (fixed id)
2	:name.object_id	Get object id of :name symbol again	Same as step 1, e.g. 123456
3	:name.object_id == :name.object_id	Compare object ids	true (same object)
4	:name.to_s	Convert symbol to string	"name"
5	name = :name	Assign symbol :name to variable name	Variable name points to symbol :name
6	name = :other	Assign symbol :other to variable name	Variable name points to symbol :other

💡 Symbols are immutable and reused, so object ids for the same symbol are always equal.

Variable Tracker

Variable	Start	After Step 5	After Step 6
name	undefined	:name (symbol)	:other (symbol)

Key Moments - 3 Insights

Why does :name.object_id return the same value every time?

Because symbols are stored once in memory and reused, so the object id is always the same for the same symbol (see steps 1, 2, and 3).

Can we change the content of a symbol like a string?

No, symbols are immutable, so you cannot change their content. Converting to string (:name.to_s) creates a new string but does not change the symbol (see step 4).

Does assigning a new symbol to a variable create a new symbol object?

No, symbols are created once and reused. Assigning a new symbol just points the variable to a different existing symbol (see steps 5 and 6).

Visual Quiz - 3 Questions

Look at the execution table, what is the result of comparing :name.object_id == :name.object_id at step 3?

A true

B false

C nil

D error

💡 Hint

Check step 3 in the execution_table where the comparison is made.

At which step does the variable name change to point to a different symbol?

A Step 4

B Step 5

C Step 6

D Step 3

💡 Hint

Look at variable_tracker and execution_table steps 5 and 6.

If symbols were mutable, what would change in the execution table?

A The object ids would differ for the same symbol

B The comparison at step 3 would be false

C The to_s method would change the symbol itself

D Assigning a new symbol would create a new object id

💡 Hint

Refer to key_moments about immutability and step 3 comparison.

Concept Snapshot

Symbols are unique, immutable names stored once in memory.
They have a fixed object id reused everywhere.
Symbols cannot be changed like strings.
Assigning symbols just points variables to existing symbols.
Use symbols for identifiers needing fast, memory-efficient reuse.

Full Transcript

Symbols in Ruby are special names that are stored only once in memory. When you write :name multiple times, Ruby uses the same symbol object each time. This means the object id of :name is always the same, as shown in steps 1, 2, and 3. Symbols are immutable, so you cannot change their content like strings. For example, :name.to_s returns a string "name" but does not change the symbol itself (step 4). When you assign a symbol to a variable, like name = :name or name = :other, you are just pointing the variable to an existing symbol object (steps 5 and 6). This makes symbols very efficient for identifiers that do not need to change. Understanding that symbols are immutable and reused helps avoid confusion about object ids and variable assignments.

Practice

1.

What is a key characteristic of a Ruby Symbol?

easy

A. It is immutable and unique for the same name

B. It can be changed after creation

C. It stores large amounts of data

D. It behaves like a string with spaces

Solution

1. Step 1: Understand what a Symbol is

   A Symbol in Ruby is a name or label that is immutable, meaning it cannot be changed once created.

2. Step 2: Recognize uniqueness of Symbols

   Two Symbols with the same name always refer to the same object, making them unique and memory efficient.

3. Final Answer:

   It is immutable and unique for the same name -> Option A

4. Quick Check:

   Symbol = immutable and unique [OK]

Hint: Symbols never change and are unique by name [OK]

Common Mistakes:

• Thinking symbols can be modified like strings
• Confusing symbols with regular strings
• Assuming symbols store large data
• Believing symbols allow spaces like strings

2.

Which of the following is the correct way to write a Ruby symbol?

?

easy

A. 'my_symbol'

B. "my_symbol"

C. my_symbol

D. :my_symbol

Solution

1. Step 1: Identify symbol syntax in Ruby

   Symbols are written with a colon : followed by a name without quotes.

2. Step 2: Compare options

   Only :my_symbol uses the correct symbol syntax; others are strings or invalid.

3. Final Answer:

   :my_symbol -> Option D

4. Quick Check:

   Symbol syntax = colon + name [OK]

Hint: Symbols start with a colon : followed by name [OK]

Common Mistakes:

• Using quotes around symbols
• Writing symbols without colon
• Confusing symbols with strings
• Using invalid characters in symbol names

3.

What will be the output of the following Ruby code?

sym1 = :apple
sym2 = :apple
puts sym1.object_id == sym2.object_id

medium

A. false

B. nil

C. true

D. SyntaxError

Solution

1. Step 1: Understand symbol object identity

   Symbols with the same name share the same object_id because they are unique and immutable.

2. Step 2: Compare object_ids of sym1 and sym2

   Both :apple symbols point to the same object, so their object_ids are equal, making the comparison true.

3. Final Answer:

   true -> Option C

4. Quick Check:

   Same symbol = same object_id [OK]

Hint: Same symbol names share object_id, so comparison is true [OK]

Common Mistakes:

• Assuming different symbols have different object_ids
• Confusing symbols with strings which differ
• Expecting false because of separate variables
• Thinking symbols are mutable objects

4.

Find the error in this Ruby code snippet:

sym = :hello
sym << " world"
puts sym

medium

A. Symbols can be changed with << operator

B. Symbols cannot be concatenated with <<

C. Syntax error in symbol declaration

D. Missing quotes around symbol

Solution

1. Step 1: Check symbol mutability

   Symbols are immutable, so you cannot change them or add to them with operators like <<.

2. Step 2: Identify the error in code

   The line sym << " world" tries to modify the symbol, which causes a runtime error.

3. Final Answer:

   Symbols cannot be concatenated with << -> Option B

4. Quick Check:

   Symbols are immutable, no << allowed [OK]

Hint: Symbols cannot be changed or concatenated [OK]

Common Mistakes:

• Trying to modify symbols like strings
• Assuming symbols can be concatenated
• Confusing syntax errors with runtime errors
• Using << operator on immutable objects

5.

Given the following code, what will be the output?

hash = { apple: 1, banana: 2 }
key = :apple
hash[key] = 3
puts hash[:apple]

Consider the immutability and identity of symbols in your answer.

hard

A. 3

B. 1

C. nil

D. KeyError

Solution

1. Step 1: Understand symbol keys in hash

   Symbols used as keys are immutable and unique, so :apple and key (which is :apple) refer to the same key.

2. Step 2: Update hash value for :apple

   Assigning hash[key] = 3 updates the value for the :apple key from 1 to 3.

3. Step 3: Output the updated value

   puts hash[:apple] prints the updated value 3.

4. Final Answer:

   3 -> Option A

5. Quick Check:

   Symbol keys are unique, so value updates correctly [OK]

Hint: Symbol keys are unique; updating key changes value [OK]

Common Mistakes:

• Thinking key is different because of variable
• Expecting original value 1 instead of updated 3
• Confusing symbols with strings as keys
• Assuming symbols can be duplicated in hash keys