Go Context Management FAQs

Question 1

Why should I avoid storing context in a struct?

Accepted Answer

Contexts are meant to be request-scoped and passed through the call chain; storing them in structs can lead to stale contexts, memory leaks, and race conditions during concurrent access.

Question 2

When is it appropriate to use context.TODO()?

Accepted Answer

Use context.TODO() as a temporary placeholder when you are unsure which context to use or when refactoring legacy code where context has not yet been implemented.

Question 3

How does this skill help prevent goroutine leaks?

Accepted Answer

By enforcing the use of context.WithCancel and context.WithTimeout, the skill ensures that goroutines are signaled to exit as soon as the parent operation is no longer required.

Question 4

How do I handle background tasks after an HTTP response in Go?

Accepted Answer

Use context.WithoutCancel (available in Go 1.21+) to detach a child context from the parent's cancellation while still preserving the parent's request-scoped values like trace IDs.

Question 5

What is the best way to store values in a context?

Accepted Answer

Always use custom unexported types for context keys to avoid collisions with other packages, and provide public getter/setter functions to ensure type safety when accessing values.

Go Context Management

Key Features

Use Cases

Go Context Management

Key Features

Use Cases