What consequences can arise when reading from a closed channel in Go?

Reading from a closed channel results in an immediate zero value of the channel's element type without blocking. If a second boolean return value is present, it will be false.

package main

import (
	"fmt"
)

func main() {
	ch := make(chan int, 1) // Buffered channel
	ch <- 1
	close(ch)

	val, ok := <-ch // Reading from a closed channel
	fmt.Printf("Value: %d, Open: %t\n", val, ok) // Will output "Value: 1, Open: true"

	val, ok = <-ch // Re-reading from the same closed channel
	fmt.Printf("Value: %d, Open: %t\n", val, ok) // Will output "Value: 0, Open: false"

	// Further reads from the closed channel
	val, ok = <-ch
	fmt.Printf("Value: %d, Open: %t\n", val, ok) // Will output "Value: 0, Open: false"
}

Main consequences:

• Getting zero value: The program will not crash but will receive the default zero value for the channel's data type.
• Closure indicator: The second boolean parameter, if used, becomes false, signaling that the channel is closed and the received value is zero.
• Non-blocking read: The read operation will not block the goroutine.
• No panic: Unlike writing to a closed channel, reading from a closed channel does not cause a panic.

Comparison of reading from open and closed channels:

Channel state	Operation	Behavior	Return value (if second parameter is used)
Open	<-ch	Blocks until a value is received or the channel is closed	Value, true
Open	val, ok := <-ch	Blocks until a value is received or the channel is closed	Value, true
Closed	<-ch	Immediate retrieval	Zero value
Closed	val, ok := <-ch	Immediate retrieval	Zero value, false

Using the second boolean parameter is the recommended way to determine whether a real element was successfully received from the channel or if the channel is closed.

package main

import (
	"fmt"
)

func main() {
	ch := make(chan int, 1)
	ch <- 1
	close(ch)

	for {
		val, ok := <-ch
		if !ok {
			fmt.Println("Channel is closed, exiting loop.")
			break
		}
		fmt.Printf("Received value: %d\n", val)
	}
}

This behavior allows for graceful termination of goroutines that read from the channel after it is closed.