Why select is needed in Go - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to wait on multiple channels using select.

Go

select {
case msg := <-ch1:
    fmt.Println("Received", msg)
case [1]:
    fmt.Println("Timeout")
}

Drag options to blanks, or click blank then click option'

A<-time.After(time.Second)

Bmsg := <-ch2

C<-done

D<-ch1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a receive from the wrong channel without timeout.

Not including a timeout case causing blocking.

The select statement waits on multiple channel operations. Using case <-time.After(time.Second) adds a timeout case.

2fill in blank

medium

Complete the select statement to handle messages from two channels.

Go

select {
case msg1 := <-ch1:
    fmt.Println("From ch1:", msg1)
case [1]:
    fmt.Println("From ch2:", msg2)
}

Drag options to blanks, or click blank then click option'

Amsg2 := <-ch2

Bmsg2 := <-ch1

Cmsg1 := <-ch2

Dmsg1 := <-done

Attempts:

3 left

💡 Hint

Common Mistakes

Receiving from the same channel twice.

Using wrong variable names causing confusion.

The select waits on both ch1 and ch2. The second case must receive from ch2.

3fill in blank

hard

Fix the error in the select statement to avoid blocking.

Go

select {
case msg := <-ch1:
    fmt.Println(msg)
[1]:
    fmt.Println("No message received")
}

Drag options to blanks, or click blank then click option'

Acase msg := <-ch2

Bcase <-time.After(time.Second)

Ccase <-done

Ddefault

Attempts:

3 left

💡 Hint

Common Mistakes

Using a timeout channel instead of default when immediate fallback is needed.

Omitting default causing the program to block.

The default case in select runs if no other case is ready, preventing blocking.

4fill in blank

hard

Fill both blanks to create a select that handles two channels and a default case.

Go

select {
case msg := <-ch1:
    fmt.Println("ch1:", msg)
case [1]:
    fmt.Println("ch2:", msg)
default:
    fmt.Println([2])
}

Drag options to blanks, or click blank then click option'

Amsg := <-ch2

B"No messages"

Cmsg := <-done

D"Waiting..."

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong channel names in cases.

Putting a channel receive in default case.

The select listens on ch1 and ch2. The default prints a message when no channels are ready.

5fill in blank

hard

Fill all three blanks to create a select that handles two channels and a timeout.

Go

select {
case msg := <-[1]:
    fmt.Println("Received from first channel:", msg)
case msg := <-[2]:
    fmt.Println("Received from second channel:", msg)
case <-[3]:
    fmt.Println("Timeout occurred")
}

Drag options to blanks, or click blank then click option'

Ach1

Bch2

Ctime.After(time.Second)

Ddone

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up channel names.

Using a variable instead of time.After for timeout.

The select waits on ch1, ch2, and a timeout channel from time.After.

Practice

1. Why do we need the select statement in Go when working with channels?

easy

A. To convert channels into slices

B. To create new channels dynamically

C. To wait on multiple channels and handle whichever is ready first

D. To close channels safely

Solution

1. Step 1: Understand the purpose of select

   The select statement allows a Go program to wait on multiple channel operations simultaneously.

2. Step 2: Identify what select does

   It picks the first channel that is ready to send or receive and executes the corresponding code block.

3. Final Answer:

   To wait on multiple channels and handle whichever is ready first -> Option C

4. Quick Check:

   select waits on many channels = D [OK]

Hint: Remember: select waits on many channels at once [OK]

Common Mistakes:

• Thinking select creates or closes channels
• Confusing select with channel creation syntax
• Assuming select converts channels to other types

2. Which of the following is the correct syntax to start a select block in Go?

easy

A. for { case <-ch1: ... case <-ch2: ... }

B. switch { case <-ch1: ... case <-ch2: ... }

C. if { case <-ch1: ... case <-ch2: ... }

D. select { case <-ch1: ... case <-ch2: ... }

Solution

1. Step 1: Recall the syntax for select

   The select statement uses curly braces and multiple case clauses for channels.

2. Step 2: Match the correct syntax

   select { case <-ch1: ... case <-ch2: ... } correctly shows select { case <-ch1: ... case <-ch2: ... }, which is valid Go syntax.

3. Final Answer:

   select { case <-ch1: ... case <-ch2: ... } -> Option D

4. Quick Check:

   Correct select syntax = A [OK]

Hint: Select uses 'select { case ... }' syntax, not switch or if [OK]

Common Mistakes:

• Using switch instead of select for channels
• Trying to use if with case clauses
• Using for loop syntax for select

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

package main
import (
  "fmt"
  "time"
)
func main() {
  ch1 := make(chan string)
  ch2 := make(chan string)
  go func() { ch1 <- "hello" }()
  go func() {
    time.Sleep(10 * time.Millisecond)
    ch2 <- "world"
  }()
  select {
  case msg1 := <-ch1:
    fmt.Println(msg1)
  case msg2 := <-ch2:
    fmt.Println(msg2)
  }
}

medium

A. hello

B. world

C. hello world

D. No output, program deadlocks

Solution

1. Step 1: Understand the goroutines sending to channels

   Two goroutines send "hello" to ch1 and "world" to ch2 concurrently.

2. Step 2: Analyze the select statement behavior

   The select picks the first channel ready to receive. The ch1 goroutine sends immediately while the ch2 goroutine sleeps for 10ms before sending, so ch1 is ready first, printing "hello".

3. Final Answer:

   hello -> Option A

4. Quick Check:

   Select picks first ready channel = hello [OK]

Hint: Select prints first ready channel message only [OK]

Common Mistakes:

• Expecting both messages printed
• Thinking select waits for all channels
• Assuming program deadlocks without buffering

4. Identify the error in this Go code using select:

package main
func main() {
  ch := make(chan int)
  select {
  case val := <-ch:
    println(val)
  default:
    println("No value")
  }
}

medium

A. The channel ch is not closed, causing a deadlock

B. The code is correct and prints "No value" immediately

C. The select statement must have at least two cases with channels

D. The default case is not allowed in select

Solution

1. Step 1: Understand select with default case

   If no channel is ready, the default case runs immediately without blocking.

2. Step 2: Analyze the code behavior

   Since ch is empty and no send occurs, the receive case blocks, so default prints "No value".

3. Final Answer:

   The code is correct and prints "No value" immediately -> Option B

4. Quick Check:

   Select with default runs default if no channel ready = C [OK]

Hint: Default case runs immediately if no channel ready [OK]

Common Mistakes:

• Thinking code deadlocks without channel close
• Believing select needs multiple channel cases
• Assuming default case is forbidden

5. You want to read from two channels ch1 and ch2 and process whichever sends data first. How does using select help in this scenario?

medium

A. It lets you wait on both channels simultaneously and handle the first ready one without blocking on the other

B. It merges both channels into one automatically

C. It queues messages from both channels and processes them in order

D. It duplicates messages from one channel to the other

Solution

1. Step 1: Understand the problem of waiting on multiple channels

   Without select, you would block waiting on one channel and miss data from the other.

2. Step 2: Explain how select solves this

   select waits on both channels at once and runs the code for whichever channel sends data first, making the program responsive.

3. Final Answer:

   It lets you wait on both channels simultaneously and handle the first ready one without blocking on the other -> Option A

4. Quick Check:

   Select waits on many channels and picks first ready = A [OK]

Hint: Select handles multiple channels without blocking others [OK]

Common Mistakes:

• Thinking select merges or queues channels automatically
• Assuming select duplicates messages
• Believing select processes channels sequentially