Channel synchronization in Go - Step-by-Step Execution

Concept Flow - Channel synchronization

Start main goroutine

↓

Create channel

↓

Start goroutine to send data

↓

Send data into channel

↓

Main goroutine waits to receive

↓

Receive data from channel

↓

Print received data

↓

Program ends

The main goroutine creates a channel and starts another goroutine that sends data into it. The main goroutine waits to receive data from the channel, synchronizing the two goroutines.

Execution Sample

Go

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

This Go program uses a channel to synchronize sending and receiving a string between two goroutines.

Execution Table

Step	Action	Channel State	Goroutine State	Output
1	Create channel ch	empty	main running
2	Start goroutine to send "hello"	empty	main and sender running
3	Sender tries to send "hello" into ch	blocked (waiting for receiver)	sender blocked
4	Main goroutine waits to receive from ch	blocked (waiting for sender)	main blocked
5	Sender sends "hello" into ch	contains "hello"	sender unblocked, ends
6	Main receives "hello" from ch	empty	main unblocked
7	Print "hello"	empty	main running	hello
8	Program ends	empty	all goroutines ended

💡 Program ends after main goroutine prints the received message and all goroutines finish.

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 6	Final
ch	empty	blocked (send waiting)	contains "hello"	empty	empty
msg	undefined	undefined	undefined	"hello"	"hello"

Key Moments - 3 Insights

Why does the sender goroutine block when sending to the channel?

Because the channel is unbuffered, the sender waits until the main goroutine receives the value, as shown in step 3 of the execution_table.

How does the main goroutine know when to continue after waiting on the channel?

It continues after receiving the value from the channel, which unblocks it as shown in step 6 of the execution_table.

What happens if the main goroutine tries to receive before the sender sends?

The main goroutine blocks and waits until the sender sends a value, ensuring synchronization, as seen in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the sender goroutine unblock?

A Step 5

B Step 6

C Step 3

D Step 7

💡 Hint

Check the 'Goroutine State' column for the sender goroutine status.

According to variable_tracker, what is the state of channel 'ch' after step 6?

A contains "hello"

B empty

C blocked (send waiting)

D closed

💡 Hint

Look at the 'ch' row under 'After Step 6' in variable_tracker.

If the channel was buffered with capacity 1, how would the sender's state at step 3 change?

A Sender would never send

B Sender would block waiting for receiver

C Sender would send immediately without blocking

D Sender would panic

💡 Hint

Buffered channels allow sending without immediate receiver if buffer space is available.

Concept Snapshot

Channel synchronization in Go:
- Create channel with make(chan Type)
- Sending blocks until receiver is ready (unbuffered channel)
- Receiving blocks until sender sends
- Synchronizes goroutines by waiting on send/receive
- Use channels to safely share data between goroutines

Full Transcript

This example shows how Go uses channels to synchronize two goroutines. The main goroutine creates an unbuffered channel and starts a sender goroutine. The sender tries to send a string into the channel but blocks because the main goroutine has not yet received it. The main goroutine waits to receive from the channel, which unblocks the sender. After the sender sends the string, the main goroutine receives it and prints it. This synchronization ensures safe communication between goroutines without race conditions.

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