Common Channel Mistakes and Deadlocks in Go

Deadlocks in Go occur when goroutines block indefinitely waiting for channel operations that never complete, often due to unbuffered channels or missing sends/receives. Use buffered channels or ensure every send has a corresponding receive to prevent blocking.

// Deadlock: Unbuffered channel blocks if no receiver is ready
ch := make(chan int)
ch <- 1 // Blocks forever if no other goroutine reads from ch

// Fix: Use a buffered channel or add a receiver
ch := make(chan int, 1)
ch <- 1 // Non-blocking with buffer size 1

// Or ensure a receiver exists
ch := make(chan int)
go func() { <-ch }() // Receiver ready
ch <- 1 // Now safe

A deadlock happens when two or more parts of your program wait for each other forever, like two people trying to talk but neither speaks first. In Go, this often occurs with channels if you try to send data without anyone ready to receive it, or vice versa. Think of it as a traffic jam where cars block each other and none can move.