Blocking behavior in Go

Introduction

Blocking behavior means a program waits for something to finish before moving on. It helps control the order of tasks.

When you want to wait for a task to finish before starting another.

When reading data from a channel and you need to wait until data is available.

When you want to pause a program until a user input or event happens.

When synchronizing multiple parts of a program to work step-by-step.

When you want to make sure a resource is ready before using it.

Syntax

Go

value := <-channel
// This line waits (blocks) until a value is received from the channel

Receiving from a channel blocks the program until data is ready.

Sending to a channel also blocks if the channel is full or unbuffered.

Examples

The program waits at the receive line until some data is sent to ch.

Go

ch := make(chan int)

// This will block because no one sends data yet
value := <-ch

Buffered channels allow some sends without blocking until the buffer is full.

Go

ch := make(chan int, 1)

ch <- 5 // This does not block because channel has buffer
ch <- 10 // This blocks because buffer is full

This waits for the goroutine to finish by blocking on done channel receive.

Go

done := make(chan bool)
go func() {
    // Do some work
    done <- true // Signal completion
}()
<-done // Wait here until work is done

Sample Program

This program starts a goroutine that waits 2 seconds then sends a message. The main function waits (blocks) on the channel receive until the message arrives, then prints it.

Go

package main

import (
	"fmt"
	"time"
)

func main() {
	ch := make(chan string)

	go func() {
		time.Sleep(2 * time.Second)
		ch <- "Hello from goroutine"
	}()

	fmt.Println("Waiting for message...")
	msg := <-ch // This line blocks until message arrives
	fmt.Println("Received message:", msg)
}

Important Notes

Blocking is normal and useful in Go for synchronization.

Too much blocking can freeze your program, so use goroutines to run tasks concurrently.

Buffered channels can reduce blocking but need careful size management.

Summary

Blocking means waiting for something to finish before continuing.

Receiving or sending on channels can cause blocking in Go.

Use blocking to coordinate tasks and control program flow.

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