GO Channels and Communication 3

Question 1

What is the fan-in concurrency pattern?

Accepted Answer

Multiple channels are merged into one output channel

Answer

One goroutine writes to many channels

Answer

A channel is read in a loop

Answer

Channels are nested inside structs

Question 2

How do you check if a channel receive returned a real value or a closed-channel zero value?

Accepted Answer

v, ok := <-ch; check ok

Answer

v == nil

Answer

len(ch) > 0

Answer

cap(ch) > 0

Question 3

What does `len(ch)` return for a buffered channel?

Accepted Answer

Number of elements currently buffered

Answer

Channel capacity

Answer

Number of goroutines waiting to send

Answer

Always 0

Question 4

What is a done channel pattern used for?

Accepted Answer

Signal goroutines to stop working and exit

Answer

Limit channel buffer size

Answer

Synchronize goroutine start times

Answer

Measure goroutine performance

Question 5

Why is `chan struct{}` preferred over `chan bool` for signaling in Go?

Accepted Answer

struct{} consumes zero bytes, minimizing memory overhead

Answer

struct{} has faster sends

Answer

bool channels do not support close

Answer

struct{} channels are unbuffered by default

Question 6

What is a pipeline pattern in Go?

Accepted Answer

A series of stages connected by channels, each processing and passing data

Answer

Chaining functions without channels

Answer

A single goroutine processing a list

Answer

Parallel sorting of a slice