go-formatter VS go-multierror

A curated list of awesome Go frameworks, libraries and software - Awesome Go / Golang (awesome-go.com)

Awesome Go projects and frmaeworks

Go: https://github.com/avelino/awesome-go

✨ Includes all packages from Awesome Go ✨ (some entries did not exist anymore)

Awesome Go projects and frmaeworks

AFAIK, no. There are some helper frameworks [1], but none of them is dominant. Two possible reasons: it's quite easy to write a (web) service with the library functions (it even includes a gzip stream), and it's practically impossible to write an ORM framework like you have in Java and Python, so the Go frameworks I've seen are basically a bunch of helper functions.

[1] https://github.com/avelino/awesome-go#web-frameworks

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.