Why slices are used in Go - See It in Action

Why slices are used

📖 Scenario: Imagine you are organizing a list of your favorite fruits. You want to keep track of them and sometimes add more fruits without creating a new list every time.

🎯 Goal: You will create a slice of fruits, add more fruits to it, and print the final list. This will show why slices are useful in Go for flexible and efficient list handling.

📋 What You'll Learn

Create a slice of strings called fruits with initial values: "Apple", "Banana", "Cherry"

Create a new slice called moreFruits with values: "Date", "Elderberry"

Append moreFruits to fruits using the append function

Print the final fruits slice

💡 Why This Matters

🌍 Real World

Slices are used in Go programs to handle lists of data that can change size, like user inputs, file lines, or database records.

💼 Career

Understanding slices is essential for Go developers because they provide efficient and flexible ways to manage collections of data in real-world applications.

1

Create the initial slice of fruits

Create a slice of strings called fruits with these exact values: "Apple", "Banana", "Cherry"

Go

// Create the slice fruits with "Apple", "Banana", "Cherry"
// Your code here

Hint

Use []string{} to create a slice with the given fruits.

2

Create a new slice of more fruits

Create a slice of strings called moreFruits with these exact values: "Date", "Elderberry"

Go

package main

import "fmt"

func main() {
    fruits := []string{"Apple", "Banana", "Cherry"}
    // Create the slice moreFruits with "Date", "Elderberry"
    // Your code here
}

Hint

Use the same slice syntax as before to create moreFruits.

3

Append more fruits to the original slice

Use the append function to add all elements of moreFruits to the fruits slice and update fruits with the result

Go

package main

import "fmt"

func main() {
    fruits := []string{"Apple", "Banana", "Cherry"}
    moreFruits := []string{"Date", "Elderberry"}
    // Append moreFruits to fruits
    // Your code here
}

Hint

Use append(fruits, moreFruits...) to add all elements from moreFruits.

4

Print the final fruits slice

Write a fmt.Println statement to print the fruits slice

Go

package main

import "fmt"

func main() {
    fruits := []string{"Apple", "Banana", "Cherry"}
    moreFruits := []string{"Date", "Elderberry"}
    fruits = append(fruits, moreFruits...)
    // Print the fruits slice
    // Your code here
}

Hint

Use fmt.Println(fruits) to display the slice.

Practice

1.

Why are slices preferred over arrays in Go?

easy

A. Because arrays cannot store multiple values

B. Because slices use less memory than arrays

C. Because slices can change size dynamically while arrays have fixed size

D. Because slices are slower but more secure

Solution

1. Step 1: Understand array size behavior

   Arrays in Go have a fixed size defined at creation and cannot grow or shrink.

2. Step 2: Understand slice flexibility

   Slices are built on arrays but can dynamically change size, making them more flexible for varying data.

3. Final Answer:

   Because slices can change size dynamically while arrays have fixed size -> Option C

4. Quick Check:

   Slice size flexibility = A [OK]

Hint: Remember: slices grow, arrays don't [OK]

Common Mistakes:

• Thinking arrays can resize dynamically
• Confusing memory usage between slices and arrays
• Believing slices are slower than arrays

2.

Which of the following is the correct way to declare a slice of integers in Go?

var s _____

easy

A. []int

B. [5]int

C. int[]

D. slice int

Solution

1. Step 1: Recall slice syntax

   In Go, slices are declared with square brackets and no size: []type.

2. Step 2: Identify correct option

   []int uses []int which is the correct syntax for a slice of integers.

3. Final Answer:

   []int -> Option A

4. Quick Check:

   Slice declaration = []int [OK]

Hint: Slices use []type without size [OK]

Common Mistakes:

• Using fixed size like [5]int for slices
• Writing type after brackets like int[]
• Using invalid keywords like 'slice int'

3.

What will be the output of this Go code?

arr := [3]int{1, 2, 3}
slice := arr[:2]
slice = append(slice, 4)
fmt.Println(arr)

medium

A. [1 2 4]

B. [1 2 3 4]

C. [1 2 3]

D. Runtime error

Solution

1. Step 1: Understand slice and array relation

   The slice references the first two elements of arr: [1, 2], with length 2 and capacity 3.

2. Step 2: Append behavior on slice

   Appending 4 to slice: since current length 2 < capacity 3, it appends in place to the underlying array, setting arr[2] = 4. Thus, arr becomes [1 2 4].

3. Final Answer:

   [1 2 4] -> Option A

4. Quick Check:

   Append within capacity modifies underlying array = B [OK]

Hint: Append within capacity modifies shared array [OK]

Common Mistakes:

• Thinking append always reallocates a new array
• Expecting arr to grow to 4 elements
• Thinking append causes runtime error

4.

Identify the error in this Go code snippet:

var s []int
s[0] = 10
fmt.Println(s)

medium

A. Syntax error: slice declaration is incorrect

B. Slice s is nil and has no elements, so s[0] assignment causes runtime panic

C. No error, code prints [10]

D. Compile error: cannot assign to slice element

Solution

1. Step 1: Check slice initialization

   Variable s is declared but not initialized; it is nil with length 0.

2. Step 2: Understand assignment to s[0]

   Assigning to s[0] causes runtime panic because no elements exist yet.

3. Final Answer:

   Slice s is nil and has no elements, so s[0] assignment causes runtime panic -> Option B

4. Quick Check:

   Assigning to nil slice index = runtime panic [OK]

Hint: Initialize slice before assigning elements [OK]

Common Mistakes:

• Assuming slice auto-expands on index assignment
• Thinking code compiles with no error
• Confusing compile error with runtime panic

5.

You want to collect an unknown number of user scores efficiently. Which approach best uses slices?

1. Use a fixed-size array
2. Use a slice and append scores as they come
3. Use a map with indexes
4. Use a string to store scores

hard

A. Use a fixed-size array

B. Use a string to store scores

C. Use a map with indexes

D. Use a slice and append scores as they come

Solution

1. Step 1: Consider data size flexibility

   User scores count is unknown, so fixed-size array is not suitable.

2. Step 2: Evaluate slice usage

   Slices can grow dynamically and efficiently handle unknown data sizes by appending.

3. Step 3: Exclude other options

   Maps add overhead and strings are not suitable for numeric data storage.

4. Final Answer:

   Use a slice and append scores as they come -> Option D

5. Quick Check:

   Dynamic data collection = slice append [OK]

Hint: Use slices to grow lists dynamically [OK]

Common Mistakes:

• Choosing fixed arrays for unknown sizes
• Using strings for numeric data
• Overcomplicating with maps when slices suffice