multierr VS go-multierror

The only remaining use-case I see here looks like https://github.com/uber-go/multierr , maybe useful in concurrent scenarios. But on my side this is rather anecdotical, and anyway already addressed by a well documented and tested third party.

There are a few libraries that solve this problem. One is https://github.com/uber-go/multierr , another https://github.com/hashicorp/go-multierror . They have similar APIs and are pretty easy to use. If you don't want to import another library, it's pretty easy to do something similar yourself, inspired by them. 😊

Some packages offer utilities to gather results from goroutines, such as multierror.Group or parallel.Map in samber/lo.

I've created a simple Go library for managing concurrent tasks, results, and errors. Inspired by HashiCorp's go-multierror, it simplifies running goroutines, collecting results, and error handling by minimizing boilerplate code.

This looks great and can be integrated into ORM. What about adopting go-multierror?

Unlike errgroup, github.com/hashicorp/go-multierror cannot be interrupted by context. However, it is useful for use cases where you need to check all errors and handle them carefully, because you can keep all errors.

I found that it was also useful to introduce https://github.com/hashicorp/go-multierror so if one or more single work items returns an error, we can also batch the errors as a single thing.