goneric | conc | |
---|---|---|
5 | 23 | |
18 | 8,444 | |
- | 1.8% | |
4.1 | 5.9 | |
about 1 year ago | 16 days ago | |
Go | Go | |
MIT License | 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.
goneric
-
(Rust) Tokio, FuturesUnordered, and the Thundering Herd Problem
Only thing missing from making it look and work as traditional async is lack of pre-processor to make it "look nice". Generics do make it a bit better, for example from my lib you can introduce some concurrency quite easily, for example
-
Conc: Better Structured Concurrency for Go
I do like idea of waitgroup on steroids, I might steal it for my generic library.
* [1] https://github.com/XANi/goneric/blob/master/worker.go#L92
-
Have yet to use generics...Am I missing out?
Shameless plug: here is a list of some useful stuff you can do with it, with code attached.
-
I've created a Go Generics cheatsheet to give you a quick reminder of how to use this feature
If someone wants some more examples I've made a lib with a bunch of common constructs. Fun ones include "run function in parallel on a slice and put it in output slice in order" or "return which elements are different between slices", with version allowing to easily get difference between 2 different types using conversion function
- Spawn multiple go routines, get the results back, in order of goroutine spawn...
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?
dskDitto - Super fast duplicate file finder written in Golang.
ants - πππ ants is a high-performance and low-cost goroutine pool in Go./ ants ζ―δΈδΈͺι«ζ§θ½δΈδ½ζθη goroutine ζ± γ
go-future - A futures concurrency library in go
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-recovery - Golang recover from panics
go-waitgroup - A sync.WaitGroup with error handling and concurrency control
generic-worker-pool - Go (1.18+) framework to run a pool of N workers
advent-of-code-2022 - Advent of Code 2022
tunny - A goroutine pool for Go
lo - π₯ A Lodash-style Go library based on Go 1.18+ Generics (map, filter, contains, find...)
goworker - goworker is a Go-based background worker that runs 10 to 100,000* times faster than Ruby-based workers.