Does context.Context provide a mechanism to forcibly terminate a non-responsive goroutine?

Goroutine Termination and Context Propagation

In Go, the context package is the standard for propagating cancellation signals and timeouts across API boundaries. By using context.WithCancel or context.WithTimeout, a parent context can signal to child goroutines that an operation should be aborted via the Done() channel.

However, the design of Go concurrency relies on cooperative multitasking. A goroutine must actively poll the Done() channel within a select block to acknowledge a cancellation signal and exit gracefully.

This creates a challenge when dealing with blocking operations or tight loops that do not check the context state, as there is no built-in primitive to kill a goroutine from the outside.

• How does Go handle scenarios where a goroutine ignores the Done() signal?
• Is there a documented pattern to ensure resource reclamation when a child goroutine becomes non-responsive to context cancellation?