go-multierror
conc
go-multierror | conc | |
---|---|---|
16 | 23 | |
2,197 | 8,472 | |
1.4% | 2.1% | |
4.6 | 5.9 | |
4 days ago | 30 days ago | |
Go | Go | |
Mozilla Public License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-multierror
-
In what ways are channels are better than the traditional await?
Some packages offer utilities to gather results from goroutines, such as multierror.Group or parallel.Map in samber/lo.
-
ResultGroup: Go lib for concurrent tasks & errors management
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.
-
Valgo is a type-safe, expressive, and extensible validator library for Golang.
This looks great and can be integrated into ORM. What about adopting go-multierror?
- Multiple error wrapping is coming in Go 1.20
- mdobak/go-xerrors: Yet another error handling library.
-
Multiple error handling in Go
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.
- A simple and easy-to-use batch error implementation.
- Better error handling in Golang: Theory and practical tips
-
SimpleFlow - Simplified generic workflows and concurrency patterns
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.
- If you absolutely must create a generic Optional…
conc
-
The Case of a Leaky Goroutine
It's a pity Go didn't have structured concurrency: https://vorpus.org/blog/notes-on-structured-concurrency-or-g...
There's a library for it: https://github.com/sourcegraph/conc
But this goes to one of the things I've been kind of banging on about languages, which is that if it's not in the language, or at least the standard library right at the beginning, sometimes it almost might as well not exist. Sometimes a new language can be valuable, even if it has no "new" language features, just to get a chance to reboot the standard library it has and push for patterns that older languages are theoretically capable of, but they just don't play well with any of the libraries in the language. Having it as a much-later 3rd party library just isn't good enough.
(In fact if I ever saw a new language start up and that was basically its pitch, I'd be very intrigued; it would show a lot of maturity in the language designer.)
-
Go CLI to calculate total media duraton in directories
What are possible use cases for this tool? Why would I want to find out the total runtime of all videos in a directory?
Also, you might wanna limit concurrency[0] instead of spawning many ffprobe instances at the ~same time.
[0]: https://github.com/sourcegraph/conc
In another note, ChatGPT suggests this shell command to do the same thing. It doesn't process files in parallel though.
find . -name "*.mp4" -print0 | \
- Building conc: Better structured concurrency for Go
-
The compact overview of JDK 21’s “frozen” feature list
While virtual threads will be stable in Java 21, Structured Concurrency is still a preview feature. You probably won't see it in production anytime soon.
Preview features require a special flag when compiling and running them, and they won't run on newer versions of the JVM. I don't expect to see StructuredTaskScope in common production use before the next LTS version is out.
But it doesn't mean you cannot have structured concurrency before that. Even in language that mostly enforce Structured Concurrency like Kotlin, it's still a library feature. Even the original blog post which formulated this concept, described a library that implemented structured concurrency for Python[1]. You can pretty easily implement structured concurrency yourself by creating your own implementation of StructuredTaskScope, if you need it right now. You can even structured concurrency in C#[2] or Go[3].
[1] https://vorpus.org/blog/notes-on-structured-concurrency-or-g...
[2] https://github.com/StephenCleary/StructuredConcurrency
[3] https://github.com/sourcegraph/conc
-
Could I get a code review?
I'm also a fan of Conc for managing various different concurrency patterns -- don't create manual worker pools for locally distributed tasks if you can use Conc, etc.
-
ResultGroup: Go lib for concurrent tasks & errors management
How does this compare to conc?
-
Hello gophers, show me your concurrent code
I will probably be using more conc too now. Lots of great primitives for dealing with multiple functions returning the same types or errors etc.
-
A lot of boilerplate code when writing asynchronous code in go
You want a fast asynchronous development use a library I recommend https://github.com/sourcegraph/conc
-
About goroutine pool
A struct{} channel is the way standard way to implement this - yes. I don't think we're saying anything different? Here's a good implementation I used recently: https://github.com/sourcegraph/conc/blob/main/pool/pool.go
What are some alternatives?
multierr - Combine one or more Go errors together
ants - 🐜🐜🐜 ants is a high-performance and low-cost goroutine pool in Go./ ants 是一个高性能且低损耗的 goroutine 池。
errors - Simple error handling primitives
async - A safe way to execute functions asynchronously, recovering them in case of panic. It also provides an error stack aiming to facilitate fail causes discovery.
go-chat-bot - IRC, Slack, Telegram and RocketChat bot written in go
go-waitgroup - A sync.WaitGroup with error handling and concurrency control
conv - Fast conversions across various Go types with a simple API.
generic-worker-pool - Go (1.18+) framework to run a pool of N workers
errorx - A comprehensive error handling library for Go
tunny - A goroutine pool for Go
werr
goworker - goworker is a Go-based background worker that runs 10 to 100,000* times faster than Ruby-based workers.