Why maps are used in Go - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of maps in Go

Why do programmers use maps in Go?

A To create graphical user interfaces

B To perform mathematical calculations efficiently

C To store key-value pairs for fast data lookup

D To manage concurrent processes automatically

💡 Hint

Think about how you find a phone number quickly in a phone book.

Maps store data as key-value pairs, allowing quick access to values using keys, similar to looking up a name in a dictionary.

❓ Predict Output

intermediate

Output of map lookup

What is the output of this Go code?

Go

package main
import "fmt"
func main() {
  m := map[string]int{"apple": 5, "banana": 3}
  fmt.Println(m["apple"])
}

A banana

B 0

C apple

D 5

💡 Hint

Look at the value stored for the key "apple".

The map stores 5 for the key "apple", so printing m["apple"] outputs 5.

❓ Predict Output

advanced

Map key existence check

What does this Go code print?

Go

package main
import "fmt"
func main() {
  m := map[string]int{"x": 10}
  val, ok := m["y"]
  fmt.Println(val, ok)
}

A 0 true

B 0 false

C 10 false

D 10 true

💡 Hint

Check if the key "y" exists in the map.

The key "y" is not in the map, so val is zero value 0 and ok is false.

🔧 Debug

advanced

Why does this map assignment cause a panic?

What causes the panic in this Go code?

Go

package main
func main() {
  var m map[string]int
  m["key"] = 1
}

A The map is nil and not initialized before assignment

B The key "key" is invalid for map assignment

C The map type is incorrect for string keys

D The map must be declared with make inside main

💡 Hint

Maps must be created before use.

Declaring a map variable without initializing it results in a nil map. Assigning to a nil map causes a runtime panic.

🧠 Conceptual

expert

Why maps are preferred over slices for lookups

Why is a map preferred over a slice when you need to find an item by a key quickly?

A Maps provide constant time lookup, slices require scanning all elements

B Slices use less memory than maps for large data

C Maps keep elements in order, slices do not

D Slices automatically sort elements, maps do not

💡 Hint

Think about how fast you can find a word in a dictionary versus a list.

Maps use hashing to find keys quickly in constant time, while slices require checking each element until the key is found.

Practice

1. Why are maps used in Go programming?

easy

A. To create graphical user interfaces

B. To perform mathematical calculations

C. To store data with keys for fast lookup

D. To handle file input and output

Solution

1. Step 1: Understand the purpose of maps

   Maps store data in key-value pairs, allowing quick access to values using keys.

2. Step 2: Compare with other uses

   Maps are not used for calculations, GUI, or file handling, which are handled by other packages or types.

3. Final Answer:

   To store data with keys for fast lookup -> Option C

4. Quick Check:

   Maps = Fast key-based data access [OK]

Hint: Maps = key-value pairs for quick data access [OK]

Common Mistakes:

• Confusing maps with slices or arrays
• Thinking maps are for calculations
• Assuming maps handle files or UI

2. Which of the following is the correct way to create a map in Go?

easy

A. var m = map[string]int{1, 2, 3}

B. var m map[string]int = make(map[string]int)

C. var m = []int{1, 2, 3}

D. var m = make([]string, 5)

Solution

1. Step 1: Identify correct map creation syntax

   Maps are created using make with the syntax: make(map[keyType]valueType).

2. Step 2: Check each option

   var m map[string]int = make(map[string]int) uses make with map[string]int correctly. Options B and D create slices, and A has wrong map literal syntax.

3. Final Answer:

   var m map[string]int = make(map[string]int) -> Option B

4. Quick Check:

   Use make(map[key]value) to create maps [OK]

Hint: Use make(map[keyType]valueType) to create maps [OK]

Common Mistakes:

• Using slice syntax instead of map
• Forgetting to use make before adding items
• Incorrect map literal syntax

3. What will be the output of the following Go code?

m := make(map[string]int)
m["apple"] = 5
m["banana"] = 3
fmt.Println(m["apple"] + m["banana"])

medium

A. 53

B. Compilation error

C. 0

D. 8

Solution

1. Step 1: Understand map assignments

   Keys "apple" and "banana" are assigned values 5 and 3 respectively in the map.

2. Step 2: Calculate the sum of values

   Adding m["apple"] (5) and m["banana"] (3) results in 8.

3. Final Answer:

   8 -> Option D

4. Quick Check:

   5 + 3 = 8 [OK]

Hint: Sum values by keys to get output [OK]

Common Mistakes:

• Concatenating values as strings
• Expecting zero for missing keys
• Thinking code has syntax errors

4. What is wrong with this Go code snippet?

var m map[string]int
m["key"] = 10
fmt.Println(m["key"])

medium

A. Map is not initialized with make before use

B. Key type should be int, not string

C. Value type should be string, not int

D. fmt.Println cannot print map values

Solution

1. Step 1: Check map initialization

   The map m is declared but not initialized with make, so it is nil and cannot store values.

2. Step 2: Understand consequences

   Assigning to a nil map causes a runtime panic. The map must be created with make before adding items.

3. Final Answer:

   Map is not initialized with make before use -> Option A

4. Quick Check:

   Use make to initialize maps before adding keys [OK]

Hint: Always initialize maps with make before adding items [OK]

Common Mistakes:

• Forgetting to initialize map before use
• Confusing map declaration with initialization
• Assuming fmt.Println can't print map values

5. You want to count how many times each word appears in a list of words using a map in Go. Which approach is correct?

hard

A. Create a map[string]int with make, then loop words and increment counts

B. Use a slice of strings and append each word multiple times

C. Create a map[int]string and store counts as keys

D. Use a single string variable to store all words concatenated

Solution

1. Step 1: Choose correct data structure

   Counting word occurrences requires a map with words as keys and counts as values, so map[string]int is suitable.

2. Step 2: Implement counting logic

   Initialize the map with make, then loop through the list, incrementing the count for each word key.

3. Final Answer:

   Create a map[string]int with make, then loop words and increment counts -> Option A

4. Quick Check:

   Use map[string]int to count word frequencies [OK]

Hint: Use map[string]int and increment counts in loop [OK]

Common Mistakes:

• Using slices instead of maps for counting
• Mixing key and value types in map
• Storing counts as keys instead of values