Symbol keys vs string keys decision in Ruby - Quick Revision & Key Differences

Recall & Review

beginner

What is a symbol key in Ruby?

A symbol key is a lightweight, immutable identifier often used as a hash key. It is written with a colon, like :name, and is more memory-efficient than strings.

beginner

How do string keys differ from symbol keys in Ruby hashes?

String keys are mutable objects and can be changed, while symbol keys are immutable and unique. String keys take more memory and processing time compared to symbol keys.

intermediate

Why might you choose symbol keys over string keys in Ruby hashes?

Symbol keys are faster and use less memory because Ruby reuses the same symbol object. They are good when keys are fixed and repeated often, like configuration or options.

intermediate

When is it better to use string keys instead of symbol keys?

Use string keys when keys come from user input or external sources, or when keys need to be mutable or manipulated as strings.

beginner

What happens if you use string keys and symbol keys interchangeably in a Ruby hash?

They are treated as different keys. For example, { 'name' => 'Alice', :name => 'Bob' } has two separate entries because strings and symbols are not the same.

Which of these is a symbol key in Ruby?

A age:

B "age"

C age

D :age

A symbol key starts with a colon, like :age.

Why are symbol keys generally preferred over string keys for fixed hash keys?

A They can store numbers

B They are mutable and can be changed

C They use less memory and are faster

D They are easier to convert to strings

Symbol keys are immutable and reused, so they use less memory and are faster.

What happens if you use both :name and "name" as keys in the same Ruby hash?

A They are treated as different keys

B They refer to the same key

C They cause an error

D The string key overwrites the symbol key

Symbols and strings are different objects, so they create separate keys.

When should you prefer string keys over symbol keys?

A When keys are fixed and repeated

B When keys come from user input or external sources

C When you want faster access

D When keys are immutable

String keys are better for dynamic or external data that might change.

Which statement about symbol keys is true?

A Symbols are unique and immutable

B Symbols are mutable and can be changed

C Symbols use more memory than strings

D Symbols cannot be used as hash keys

Symbols are unique and immutable, making them efficient as hash keys.

Explain the main differences between symbol keys and string keys in Ruby hashes.

Think about memory, mutability, and when keys come from external sources.

Describe a situation where you would choose string keys over symbol keys in a Ruby program.

Consider dynamic data or external sources.

Practice

1. Which key type is best to use in a Ruby hash when the keys are fixed and known in advance?

easy

A. Symbols, because they are faster and use less memory.

B. Strings, because they are easier to type.

C. Integers, because they are numeric.

D. Arrays, because they can hold multiple values.

Solution

1. Step 1: Understand key types in Ruby hashes

   Symbols are immutable and unique, making them efficient for fixed keys.

2. Step 2: Compare symbols and strings for fixed keys

   Symbols use less memory and are faster than strings when keys do not change.

3. Final Answer:

   Symbols, because they are faster and use less memory. -> Option A

4. Quick Check:

   Fixed keys = Symbols [OK]

Hint: Use symbols for fixed keys to save memory and speed [OK]

Common Mistakes:

• Using strings for fixed keys wastes memory
• Confusing symbols with strings
• Thinking integers or arrays are valid hash keys here

2. Which of the following is the correct NEW STYLE syntax to define a Ruby hash with symbol keys?

easy

A. { 'name' => 'Alice', 'age' => 30 }

B. { name: 'Alice', age: 30 }

C. { :name => 'Alice', :age => 30 }

D. { name => 'Alice', age => 30 }

Solution

1. Step 1: Recognize Ruby symbol key syntax

   Ruby allows symbol keys with the syntax key: value (new style) or :key => value (old style).

2. Step 2: Identify the correct syntax among options

   { name: 'Alice', age: 30 } uses the modern symbol key syntax: name: 'Alice', age: 30.

3. Final Answer:

   { name: 'Alice', age: 30 } -> Option B

4. Quick Check:

   Symbol keys use key: value syntax [OK]

Hint: Use key: value for symbol keys in Ruby hashes [OK]

Common Mistakes:

• Using strings with => instead of symbols
• Missing colon before symbol keys
• Using variables as keys without symbols

3. What will be the output of this Ruby code?

person = { name: 'Bob', 'age' => 25 }
puts person[:name]
puts person['age']
puts person['name']

medium

A. Bob
25
Bob

B. nil
25
Bob

C. Bob
25

D. Bob
25
nil

Solution

1. Step 1: Understand hash keys and access

   The hash has a symbol key :name and a string key 'age'. Access must match key type exactly.

2. Step 2: Evaluate each puts statement

   person[:name] returns 'Bob'; person['age'] returns 25; person['name'] returns nil because 'name' key as string does not exist.

3. Final Answer:

   Bob 25 nil -> Option D

4. Quick Check:

   Key type must match to access value [OK]

Hint: Access hash values with exact key type used [OK]

Common Mistakes:

• Assuming symbol and string keys are interchangeable
• Expecting 'name' string key to exist when only :name symbol key is present
• Confusing output nil with empty string

4. Given this Ruby hash, what is the error in accessing the value?

settings = { 'theme' => 'dark', :font_size => 12 }
puts settings.fetch(:theme)

medium

A. KeyError because :theme symbol key does not exist.

B. No error; outputs 'dark'.

C. SyntaxError due to mixed key types.

D. RuntimeError because font_size is a symbol.

Solution

1. Step 1: Check hash keys and access

   The hash has a string key 'theme' and a symbol key :font_size.

2. Step 2: Identify the accessed key and result

   Accessing settings.fetch(:theme) looks for symbol :theme, which does not exist, raising a KeyError.

3. Final Answer:

   KeyError because :theme symbol key does not exist. -> Option A

4. Quick Check:

   Access key type must match stored key type [OK]

Hint: Match key type exactly when accessing hash values [OK]

Common Mistakes:

• Assuming string and symbol keys are interchangeable
• Expecting no error when accessing missing key
• Confusing syntax errors with key access errors

5. You have a Ruby hash where keys come from user input and can vary. Which key type should you use and why?

user_data = { ??? }

hard

A. Use symbols because they are faster and memory efficient.

B. Use arrays as keys to hold multiple user inputs.

C. Use strings because user input keys can change dynamically.

D. Use integers because they are simple and fixed.

Solution

1. Step 1: Understand key type suitability for dynamic keys

   Symbols are immutable and reused, so creating many from user input can cause memory bloat.

2. Step 2: Choose key type for user input keys

   Strings are better for dynamic or user input keys because they do not create permanent symbols.

3. Final Answer:

   Use strings because user input keys can change dynamically. -> Option C

4. Quick Check:

   Dynamic keys = Strings [OK]

Hint: Use strings for keys from user input to avoid memory issues [OK]

Common Mistakes:

• Using symbols for dynamic keys causing memory leaks
• Assuming integers or arrays are suitable keys here
• Ignoring key type impact on memory and performance