A subtle bug with Go's errgroup

TL;DR


Summary:
- The article discusses a subtle bug that can occur when using the Go `errgroup` package, which is a way to manage a group of goroutines and handle errors.
- The bug happens when you have multiple goroutines that are all trying to write to the same error variable, which can lead to race conditions and unexpected behavior.
- The article explains how to avoid this bug by using a separate error variable for each goroutine, and provides an example of how to do this correctly.

Like summarized versions? Support us on Patreon!