Channel synchronization in Go

Introduction

Channel synchronization helps different parts of a Go program talk to each other safely and wait for each other when needed.

When you want one part of your program to wait for another part to finish a task.

When you want to send data safely between different running parts (goroutines).

When you want to make sure tasks happen in order without mixing up results.

Syntax

Go

ch := make(chan Type)

// Send value to channel
ch <- value

// Receive value from channel
value := <-ch

Channels are typed, so you must specify the type of data they carry.

Sending and receiving on channels can block (wait) until the other side is ready, which helps with synchronization.

Examples

This example creates a channel for integers, sends 5 into it, and receives it back.

Go

ch := make(chan int)

// Sending
ch <- 5

// Receiving
num := <-ch

This example uses a channel to wait for a goroutine to finish its work before continuing.

Go

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

<-done // Wait for signal

Sample Program

This program starts a worker goroutine that prints a message and then signals completion through a channel. The main function waits for this signal before printing its final message.

Go

package main

import (
	"fmt"
)

func worker(done chan bool) {
	fmt.Println("Working...")
	done <- true // Signal that work is done
}

func main() {
	done := make(chan bool)
	go worker(done)
	<-done // Wait for worker to finish
	fmt.Println("Worker finished")
}

Important Notes

Channels block the sender until the receiver is ready, and vice versa, which helps coordinate tasks.

Buffered channels can hold some values without blocking, but unbuffered channels always synchronize sender and receiver.

Always close channels only when you want to signal no more values will be sent; closing a channel is not needed for synchronization.

Summary

Channels let goroutines communicate and wait for each other safely.

Sending and receiving on channels can pause execution until the other side is ready, which helps with synchronization.

Use channels to coordinate tasks and share data between goroutines without conflicts.

Practice

1. What happens when a goroutine tries to send data on an unbuffered channel if no other goroutine is ready to receive?

easy

A. The sending goroutine waits until another goroutine receives the data.

B. The data is lost and the program continues immediately.

C. The program crashes with a runtime error.

D. The data is buffered automatically for later use.

Solution

1. Step 1: Understand unbuffered channel behavior

   Unbuffered channels require both sender and receiver to be ready at the same time for communication.

2. Step 2: Analyze sending on unbuffered channel

   If no goroutine is ready to receive, the sending goroutine blocks and waits until a receiver is ready.

3. Final Answer:

   The sending goroutine waits until another goroutine receives the data. -> Option A

4. Quick Check:

   Unbuffered channel send blocks until receive [OK]

Hint: Unbuffered sends block until a receiver is ready [OK]

Common Mistakes:

• Thinking data is buffered automatically
• Assuming send never blocks
• Believing program crashes on send

2. Which of the following is the correct syntax to create a buffered channel of integers with capacity 3 in Go?

easy

A. ch := chan int{3}

B. ch := make(chan int)

C. ch := make(chan int, 3)

D. ch := new(chan int, 3)

Solution

1. Step 1: Recall channel creation syntax

   Channels are created using make with type and optional buffer size: make(chan Type, capacity).

2. Step 2: Identify correct buffered channel syntax

   To create a buffered channel of int with capacity 3, use make(chan int, 3).

3. Final Answer:

   ch := make(chan int, 3) -> Option C

4. Quick Check:

   Buffered channel syntax = make(chan Type, capacity) [OK]

Hint: Use make(chan Type, capacity) for buffered channels [OK]

Common Mistakes:

• Omitting buffer size for buffered channel
• Using new() instead of make()
• Incorrect channel literal syntax

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

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

medium

A. Compilation error

B. No output

C. Deadlock runtime error

D. hello

Solution

1. Step 1: Analyze channel and goroutine

   A goroutine sends "hello" on an unbuffered channel ch, while main receives from ch.

2. Step 2: Understand synchronization

   The send and receive synchronize, so main receives "hello" and prints it.

3. Final Answer:

   hello -> Option D

4. Quick Check:

   Send and receive synchronize, printing message [OK]

Hint: Unbuffered channel send/receive synchronize to pass data [OK]

Common Mistakes:

• Expecting deadlock because of goroutine
• Thinking channel is buffered by default
• Assuming no output due to concurrency

4. Identify the error in this Go code snippet involving channel synchronization:

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

medium

A. No error, code runs fine.

B. Sending on channel blocks forever causing deadlock.

C. Channel is not initialized properly.

D. Receiving from channel blocks forever causing deadlock.

Solution

1. Step 1: Check channel creation and usage

   Channel ch is unbuffered and created correctly with make(chan int).

2. Step 2: Analyze send operation

   Sending on unbuffered channel blocks until another goroutine receives. Here, send happens before receive, no other goroutine receives, so it blocks forever.

3. Final Answer:

   Sending on channel blocks forever causing deadlock. -> Option B

4. Quick Check:

   Send blocks without concurrent receiver [OK]

Hint: Send on unbuffered channel blocks if no receiver ready [OK]

Common Mistakes:

• Thinking receive blocks first
• Assuming channel is nil
• Believing code runs without deadlock

5. You want to run three tasks concurrently and wait for all to finish before exiting. Which Go code snippet correctly uses channels to synchronize all tasks?

hard

A. Use a buffered channel with capacity 3; each goroutine sends a signal when done; main receives 3 signals.

B. Use an unbuffered channel; main sends signals to goroutines to start; no synchronization on finish.

C. Use a buffered channel with capacity 1; goroutines send signals; main receives once.

D. Use no channels; just start goroutines and exit main immediately.

Solution

1. Step 1: Understand synchronization goal

   Main must wait for all 3 goroutines to finish before exiting.

2. Step 2: Analyze channel usage options

   Buffered channel with capacity 3 allows all goroutines to send done signals without blocking; main receives 3 signals to know all finished.

3. Final Answer:

   Use a buffered channel with capacity 3; each goroutine sends a signal when done; main receives 3 signals. -> Option A

4. Quick Check:

   Buffered channel capacity = number of goroutines to sync [OK]

Hint: Use buffered channel sized to goroutines for sync signals [OK]

Common Mistakes:

• Using unbuffered channel causing deadlock
• Receiving fewer signals than goroutines
• Not waiting for goroutines at all