String freezing for immutability in Ruby

Introduction

Freezing a string stops it from being changed. This helps keep data safe and avoids mistakes.

When you want to keep a string value the same throughout your program.

When sharing a string between parts of a program and want to prevent accidental changes.

When using strings as keys or constants that should not be modified.

When you want to improve performance by avoiding duplicate string objects.

Syntax

Ruby

string.freeze

Calling freeze on a string makes it immutable (unchangeable).

Trying to change a frozen string will cause an error.

Examples

This freezes the string stored in name.

Ruby

name = "hello"
name.freeze

This freezes the string literal "world" directly.

Ruby

"world".freeze

Check if a string is frozen using frozen? before and after freezing.

Ruby

greeting = "hi"
puts greeting.frozen?
# Output: false
greeting.freeze
puts greeting.frozen?
# Output: true

Sample Program

This program shows how freezing a string works and what happens if you try to change it after freezing.

Ruby

greeting = "hello"
puts greeting.frozen?  # false

greeting.freeze
puts greeting.frozen?  # true

# Trying to change frozen string causes error
begin
  greeting << " world"
rescue => e
  puts e.message
end

Important Notes

Freezing strings is useful to avoid bugs caused by accidental changes.

Frozen strings can improve memory usage by reusing the same object.

In Ruby 3.0+, you can use the magic comment # frozen_string_literal: true to freeze all string literals in a file.

Summary

Freezing a string makes it unchangeable.

Trying to modify a frozen string causes an error.

Use freezing to protect important string data and improve performance.

Practice

1. What does freezing a string in Ruby do?
str = "hello".freeze

easy

A. Converts the string to uppercase.

B. Deletes the string from memory.

C. Makes the string unchangeable (immutable).

D. Allows the string to be modified faster.

Solution

1. Step 1: Understand the freeze method

   The freeze method in Ruby makes an object immutable, meaning it cannot be changed after freezing.

2. Step 2: Apply to strings

   When applied to a string, it prevents any further modifications to that string's content.

3. Final Answer:

   Makes the string unchangeable (immutable). -> Option C

4. Quick Check:

   freeze means immutable = A [OK]

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

Common Mistakes:

• Thinking freeze deletes the string
• Assuming freeze changes string content
• Believing freeze speeds up modification

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

easy

A. str.freeze = "hello"

B. str = "hello".freeze

C. freeze str = "hello"

D. str = freeze("hello")

Solution

1. Step 1: Review Ruby freeze syntax

   The correct syntax to freeze a string is to call .freeze on the string object, like "hello".freeze.

2. Step 2: Check each option

   str = "hello".freeze correctly calls .freeze on the string literal. Options B, C, and D use invalid syntax or incorrect method calls.

3. Final Answer:

   str = "hello".freeze -> Option B

4. Quick Check:

   Call .freeze on string = A [OK]

Hint: Use .freeze after the string literal [OK]

Common Mistakes:

• Trying to assign freeze as a variable
• Using freeze as a standalone keyword
• Calling freeze as a function with parentheses

3. What will happen when the following Ruby code runs?

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

medium

A. The string becomes "hello world".

B. The string remains "hello" silently.

C. The string changes to " world".

D. A runtime error occurs: can't modify frozen String.

Solution

1. Step 1: Understand string freezing effect

   Freezing the string "hello" makes it immutable, so any modification attempt will raise an error.

2. Step 2: Analyze the << operation

   The << operator tries to append " world" to the frozen string, which is not allowed and causes a runtime error.

3. Final Answer:

   A runtime error occurs: can't modify frozen String. -> Option D

4. Quick Check:

   Modifying frozen string = error C [OK]

Hint: Appending to frozen string causes error [OK]

Common Mistakes:

• Assuming string changes silently
• Thinking string resets to new value
• Believing no error occurs

4. Identify the error in this Ruby code:

name = "Alice"
name.freeze
name.upcase!

medium

A. Error because upcase! tries to modify a frozen string.

B. No error; the code runs fine.

C. Error because freeze is called incorrectly.

D. Error because name is not a string.

Solution

1. Step 1: Check freeze usage

   The freeze method is correctly called on the string name, making it immutable.

2. Step 2: Understand upcase! effect

   The upcase! method tries to change the string in place, which is not allowed on a frozen string, causing a runtime error.

3. Final Answer:

   Error because upcase! tries to modify a frozen string. -> Option A

4. Quick Check:

   Modifying frozen string with upcase! = error B [OK]

Hint: In-place methods fail on frozen strings [OK]

Common Mistakes:

• Thinking freeze is called incorrectly
• Assuming no error on upcase!
• Confusing variable type

5. You want to store a constant greeting message that should never change in your Ruby program. Which approach is best?

GREETING = "Welcome!".freeze

Why is freezing important here?

hard

A. It prevents accidental changes to the greeting, ensuring data integrity.

B. It makes the greeting print faster.

C. It allows the greeting to be changed later if needed.

D. It compresses the string to save memory.

Solution

1. Step 1: Understand constant usage

   Constants like GREETING should not change during program execution to avoid bugs.

2. Step 2: Role of freeze on constants

   Freezing the string ensures it cannot be modified accidentally, protecting the constant's value.

3. Final Answer:

   It prevents accidental changes to the greeting, ensuring data integrity. -> Option A

4. Quick Check:

   Freeze constant for safety = D [OK]

Hint: Freeze constants to keep them safe from changes [OK]

Common Mistakes:

• Thinking freeze speeds up printing
• Believing freeze allows changes later
• Assuming freeze compresses data