Why Map use cases in Go? - Purpose & Use Cases

The Big Idea

What if you could find any piece of data instantly, no matter how big your list is?

The Scenario

Imagine you have a list of student names and their scores, and you want to find a student's score quickly. Without using a map, you'd have to look through the entire list every time, like searching for a friend's phone number in a long paper directory.

The Problem

Manually searching through a list is slow and tiring, especially as the list grows. It's easy to make mistakes, like missing a name or mixing up scores. This wastes time and causes frustration.

The Solution

Maps let you store data like a real-life dictionary: you look up a word (key) and get its meaning (value) instantly. This makes finding information fast and simple, no matter how big the data is.

Before vs After

✗ Before

for i := 0; i < len(students); i++ {
    if students[i].name == "Alice" {
        fmt.Println(students[i].score)
    }
}

✓ After

score := scores["Alice"]
fmt.Println(score)

What It Enables

Maps enable lightning-fast lookups and easy organization of related data, making your programs smarter and more efficient.

Real Life Example

Think of a phone contact list app: when you type a name, it instantly shows the number. Behind the scenes, it uses a map to find the number quickly without searching every contact.

Key Takeaways

Manual searching through lists is slow and error-prone.

Maps store key-value pairs for instant data lookup.

Using maps makes programs faster and easier to manage.

Practice

1. What is the primary use of a map in Go?

easy

A. To store data with keys for fast lookup

B. To perform mathematical calculations

C. To create user interfaces

D. To handle file input/output

Solution

1. Step 1: Understand the purpose of a map

   A map in Go is a collection of key-value pairs, designed for fast data retrieval using keys.

2. Step 2: Compare with other options

   Options B, C, and D describe unrelated tasks like calculations, UI, or file handling, which are not the main use of maps.

3. Final Answer:

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

4. Quick Check:

   Maps = key-value storage [OK]

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

Common Mistakes:

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

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

easy

A. m := make([]string, 0)

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

C. m := map[string]int

D. m := []int{}

Solution

1. Step 1: Identify map creation syntax

   In Go, maps are created using make(map[keyType]valueType). var m map[string]int = make(map[string]int) uses this correctly.

2. Step 2: Check other options

   m := []int{} creates a slice, not a map. m := map[string]int is invalid syntax for map creation. m := make([]string, 0) creates a slice, not a map.

3. Final Answer:

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

4. Quick Check:

   Use make() to create maps [OK]

Hint: Use make() to create maps before use [OK]

Common Mistakes:

• Using slice syntax instead of map syntax
• Not using make() to initialize maps
• Confusing map and slice creation

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

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

medium

A. 8

B. 53

C. 0

D. Compilation error

Solution

1. Step 1: Understand map assignments

   The map m stores integers with string keys. "apple" maps to 5, "banana" maps to 3.

2. Step 2: Calculate the sum

   Adding m["apple"] + m["banana"] equals 5 + 3 = 8.

3. Final Answer:

   8 -> Option A

4. Quick Check:

   5 + 3 = 8 [OK]

Hint: Sum values by accessing keys directly [OK]

Common Mistakes:

• Concatenating values as strings
• Expecting zero for existing keys
• Thinking code causes error

4. What is wrong with this Go code snippet?

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

medium

A. Cannot assign int values to map

B. Key "key" is invalid syntax

C. Map is not initialized with make() before use

D. fmt.Println cannot print map values

Solution

1. Step 1: Check map initialization

   The map m is declared but not initialized with make(). This causes a runtime panic on assignment.

2. Step 2: Understand consequences

   Without initialization, m["key"] = 10 causes a panic: assignment to nil map.

3. Final Answer:

   Map is not initialized with make() before use -> Option C

4. Quick Check:

   Initialize maps with make() [OK]

Hint: Always initialize maps with make() before adding keys [OK]

Common Mistakes:

• Forgetting to initialize map before use
• Assuming declaration is enough
• Misunderstanding map assignment rules

5. Given a map m := map[string]int{"a": 1, "b": 0, "c": 3}, which code snippet correctly checks if key "b" exists and its value is non-zero?

hard

A. if _, ok := m["b"]; ok { fmt.Println("Exists and non-zero") }

B. if m["b"] == 0 { fmt.Println("Exists and non-zero") }

C. if m["b"] >= 0 { fmt.Println("Exists and non-zero") }

D. if val, ok := m["b"]; ok && val != 0 { fmt.Println("Exists and non-zero") }

Solution

1. Step 1: Understand map key existence check

   Using val, ok := m["b"] lets us check if key "b" exists (ok) and get its value (val).

2. Step 2: Check value is non-zero

   The condition ok && val != 0 ensures key exists and value is not zero.

3. Final Answer:

   if val, ok := m["b"]; ok && val != 0 { fmt.Println("Exists and non-zero") } -> Option D

4. Quick Check:

   Check key existence and value together [OK]

Hint: Use val, ok := map[key] to check existence and value [OK]

Common Mistakes:

• Checking value without verifying key existence
• Assuming zero means key missing
• Using only ok without value check