How does the Fan-In pattern work in this skill?

The Fan-In pattern merges multiple input channels into a single output channel using a WaitGroup to track active goroutines and safely close the output once all inputs are exhausted.

What is the Or-Done pattern?

The Or-Done pattern uses a select statement to listen to both a data channel and a context's done signal, ensuring that goroutines exit early if the context is cancelled, preventing resource leaks.

When should I use buffered versus unbuffered channels?

Unbuffered channels are best for synchronous handoffs and strict synchronization, while buffered channels are used to decouple the sender and receiver to improve performance under bursty loads.

Why does this skill emphasize that only the sender should close channels?

In Go, sending to a closed channel causes a panic. By ensuring only the sender closes the channel, you prevent runtime errors that occur when a receiver closes a channel while a sender is still active.

Go Concurrency Patterns

Name: Go Concurrency Patterns
Author: JamesPrial

byJamesPrial

•

학습 및 문서화

Implements idiomatic Golang channel patterns and concurrency best practices for safe and efficient data streaming.

소개

This skill provides Claude with expert knowledge of the Go concurrency model, focusing specifically on channel-based communication and synchronization. It enforces the critical 'sender closes' rule to prevent runtime panics and promotes the use of directional channel types for improved type safety. Whether you are building high-performance backend services or complex data pipelines, this skill provides proven implementation patterns for Fan-In, Fan-Out, and Context-aware early exits (Or-Done), ensuring your goroutines remain leak-free and performant.

주요 기능

Or-Done patterns for context-aware early exits and cancellation
Strategic use of buffered vs. unbuffered channels for synchronization
2 GitHub stars
Standardized Fan-In and Fan-Out concurrency patterns
Strict guidance on directional channel types for code clarity
Enforces the 'Sender Closes' rule to prevent channel panics

사용 사례

Building high-throughput data processing pipelines in Go
Implementing graceful shutdowns and timeout handling in backend services
Managing pools of worker goroutines with synchronized output

소개

주요 기능

Or-Done patterns for context-aware early exits and cancellation
Strategic use of buffered vs. unbuffered channels for synchronization
2 GitHub stars
Standardized Fan-In and Fan-Out concurrency patterns
Strict guidance on directional channel types for code clarity
Enforces the 'Sender Closes' rule to prevent channel panics

사용 사례

Building high-throughput data processing pipelines in Go
Implementing graceful shutdowns and timeout handling in backend services
Managing pools of worker goroutines with synchronized output