Blocking behavior in Go - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does blocking behavior mean in Go?

Blocking behavior means a piece of code waits and stops running until some condition is met or an operation finishes. It pauses the current goroutine.

beginner

Which Go statement causes a goroutine to block when sending data?

Sending data on a channel blocks if the channel is unbuffered or full, making the goroutine wait until another goroutine receives the data.

beginner

How does receiving from a channel cause blocking in Go?

Receiving from a channel blocks if there is no data available yet, so the goroutine waits until some other goroutine sends data.

beginner

What happens when a goroutine calls time.Sleep() in Go?

The goroutine blocks and pauses execution for the specified time, allowing other goroutines to run meanwhile.

intermediate

Why is blocking behavior important in Go concurrency?

Blocking helps coordinate goroutines by making them wait for each other, preventing race conditions and ensuring proper data exchange.

What causes a goroutine to block when sending on an unbuffered channel?

A No goroutine is ready to receive the data

B The channel is full

C The data is too large

D The goroutine has finished

Sending on an unbuffered channel blocks until another goroutine receives the data.

What happens if you receive from an empty channel in Go?

A The program crashes

B The goroutine blocks until data is sent

C The goroutine skips the receive

D The channel closes automatically

Receiving from an empty channel blocks the goroutine until data is available.

Which Go function causes a goroutine to pause for a set time?

A close()

B fmt.Println()

C make()

D time.Sleep()

time.Sleep() blocks the goroutine for the specified duration.

Why is blocking useful in Go concurrency?

A It prevents memory leaks

B It speeds up the program

C It helps synchronize goroutines

D It avoids syntax errors

Blocking lets goroutines wait for each other, coordinating their actions safely.

What happens if you send data on a buffered channel that is full?

A The sending goroutine blocks until space is free

B The data is discarded

C The channel expands automatically

D The program panics

Sending blocks when the buffered channel is full until some data is received.

Explain what blocking behavior means in Go and give two examples where blocking happens.

Think about when a goroutine has to wait for something before continuing.

Describe why blocking is important for coordinating goroutines in Go concurrency.

Consider how goroutines communicate and share data safely.

Practice

1. What does blocking mean in Go programming?

easy

A. Running multiple tasks at the same time

B. Waiting for an operation to finish before moving on

C. Ignoring errors in the program

D. Skipping a function call

Solution

1. Step 1: Understand the meaning of blocking

   Blocking means the program waits for something to finish before continuing.

2. Step 2: Match the definition to options

   Waiting for an operation to finish before moving on correctly describes waiting for an operation to finish before moving on.

3. Final Answer:

   Waiting for an operation to finish before moving on -> Option B

4. Quick Check:

   Blocking = Waiting [OK]

Hint: Blocking means waiting, not running or skipping [OK]

Common Mistakes:

• Confusing blocking with concurrency
• Thinking blocking means ignoring errors
• Assuming blocking skips code

2. Which of the following Go code snippets correctly shows a blocking receive on a channel?

easy

A. value := <-ch

B. go func() { <-ch }()

C. ch <- value

D. select { case ch <- value: }

Solution

1. Step 1: Identify blocking receive syntax

   Receiving from a channel blocks until a value is available, done by value := <-ch.

2. Step 2: Check other options

   go func() { <-ch }() launches a goroutine, so receive is not blocking main code. ch <- value sends, not receives. select { case ch <- value: } sends in select, not receive.

3. Final Answer:

   value := <-ch -> Option A

4. Quick Check:

   Blocking receive = value := <-ch [OK]

Hint: Blocking receive uses '<-ch' without goroutine [OK]

Common Mistakes:

• Confusing send and receive syntax
• Thinking goroutine makes receive blocking
• Using select for receive incorrectly

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

package main
import "fmt"
func main() {
  ch := make(chan int)
  go func() {
    ch <- 42
  }()
  fmt.Println(<-ch)
}

medium

A. 42

B. 0

C. Compilation error

D. Deadlock runtime error

Solution

1. Step 1: Analyze channel creation and goroutine

   A channel ch is created and a goroutine sends 42 into it.

2. Step 2: Understand blocking receive

   Main goroutine waits on <-ch until value 42 is sent, then prints it.

3. Final Answer:

   42 -> Option A

4. Quick Check:

   Send and receive synchronize, output = 42 [OK]

Hint: Send in goroutine, receive blocks until value arrives [OK]

Common Mistakes:

• Expecting deadlock without goroutine
• Thinking channel defaults to zero value
• Confusing send and receive order

4. Identify the problem in this Go code and fix it:

package main
func main() {
  ch := make(chan int)
  ch <- 10
  val := <-ch
  println(val)
}

medium

A. Compilation error due to missing import; fix by adding fmt package

B. Runtime panic due to nil channel; fix by initializing channel

C. No problem; code runs and prints 10

D. Deadlock because send blocks without receiver; fix by using a goroutine for send

Solution

1. Step 1: Understand channel blocking behavior

   Sending on an unbuffered channel blocks until a receiver is ready.

2. Step 2: Analyze code flow

   Send happens before receive, but no goroutine to receive yet, causing deadlock.

3. Step 3: Fix by sending in a goroutine

   Wrap send in go func() { ch <- 10 }() to allow receive to proceed.

4. Final Answer:

   Deadlock because send blocks without receiver; fix by using a goroutine for send -> Option D

5. Quick Check:

   Send blocks without receiver = deadlock [OK]

Hint: Send blocks if no receiver; use goroutine to avoid deadlock [OK]

Common Mistakes:

• Ignoring deadlock and expecting output
• Adding imports unnecessarily
• Thinking channel is nil

5. You want to receive from two channels ch1 and ch2 but only proceed when both have sent a value. Which approach correctly uses blocking behavior to achieve this?

hard

A. Use a buffered channel to store values from both channels

B. Use a select statement with both channels in one case

C. Receive from ch1 and ch2 sequentially: val1 := <-ch1; val2 := <-ch2

D. Receive from only one channel and ignore the other

Solution

1. Step 1: Understand blocking on multiple channels

   Receiving sequentially from both channels blocks until each sends a value.

2. Step 2: Evaluate options

   Select cannot wait for both simultaneously in one case. Ignoring one channel misses data. Buffered channel does not guarantee both received.

3. Final Answer:

   Receive from ch1 and ch2 sequentially: val1 := <-ch1; val2 := <-ch2 -> Option C

4. Quick Check:

   Sequential receive blocks until both values arrive [OK]

Hint: Receive from each channel one by one to wait for both [OK]

Common Mistakes:

• Using select to wait for both at once
• Ignoring one channel's value
• Assuming buffered channel solves blocking