Thread

1. Jeeetendra · 1790509643 · focus · HN ↗

   honestly the hard part of go concurrency was never starting goroutines, it's making cancellation and shutdown behave. nice to see context, races and diagnostics in one runnable place.

   1. kccqzy · 1790535872 · focus · HN ↗

      Yup. That’s because cancellation isn’t native, but part of the context object and requires cooperation. In a language where goroutine switching is preemptive rather than cooperative, I find it odd to have cooperative cancellation, until I realize that Go doesn’t have exceptions and probably will never have them.

      1. Jeeetendra · 1790694784 · focus · HN ↗

         exactly - once you accept go has no exceptions, context cancellation is basically the least bad way to tell a goroutine to stop.

Unofficial Hacker News client; not affiliated with Y Combinator.