Hacker GitHub

← All repos

sourcegraph/conc

View on GitHub ↗ ★ 10,435 Go

Better structured concurrency for go

16 mentions on Hacker News by 16 people: 5 stories, 11 comments · first 2023-01-03 · latest 2025-10-22

Mentions per year 16 mentions · busiest year 2023 (8)
20082026
  1. waitgroup's inadequacy is why I end up using structured concurrency like https://github.com/sourcegraph/conc
    comment by dontlaugh · 2025-10-22 · in Go subtleties
  2. > Actually much closer than anything I saw in other mainstream languages eg Java or Go. https://github.com/sourcegraph/conc
  3. …although C# lets you model it to an extent). This results in community developing libraries like https://github.com/sourcegraph/conc which attempt to replicate Rust's Futures / C#'s Tasks.
    comment by neonsunset · 2025-02-28 · in 3,200% CPU Utilization
  4. Looks good, similar to https://github.com/sourcegraph/conc which we've been using for a while. Will give this a look.
  5. …similar in providing pool helpers, but doesn't provide the same fine grained batching options: https://github.com/sourcegraph/conc Uber CFF does code generation, and has more of a focus on readability and complex dependency chains:…
  6. …uses pre-generics Go. In more modern Go, you can use something like Conc to reduce the boilerplate: https://github.com/sourcegraph/conc?tab=readme-ov-file
    comment by cyberax · 2024-10-04 · in Go Concurrency vs. RxJS
  7. …speaking on whether the language should make this easier without an external library, but wouldn't https://github.com/sourcegraph/conc help in that scenario? It has context-aware and error-aware goroutine pools, seems like the exact fit…
    comment by dlisboa · 2024-06-26 · in Three ways to think about Go channels
  8. …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…
    comment by jerf · 2024-03-25 · in The case of a leaky goroutine
  9. …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…
  10. …[2] https://github.com/StephenCleary/StructuredConcurrency [3] https://github.com/sourcegraph/conc
  11. https://github.com/sourcegraph/conc/blob/main/iter/iter.go#L... // Map applies f to each element of input, returning the mapped result. func Map[T, R any](input []T, f func(*T) R) []R { res := make([]R, len(input)) ForEachIdx(input, func(i…
  12. ▲ 254
    Conc: Better Structured Concurrency for Go
    story by aurame420 · 2023-01-11 · 155 comments
  13. ▲ 3
    Conc: Better Structured Concurrency for Go
    story by ingve · 2023-01-09 · 0 comments
  14. ▲ 2
    Conc: Better Structured Concurrency for Go
    story by rtukpe · 2023-01-08 · 0 comments
  15. ▲ 4
    Sourcegraph/conc: Better structured concurrency for go
    story by kretaceous · 2023-01-04 · 0 comments
  16. ▲ 5
    Conc: Better Structured Concurrency for Go
    story by jdorfman · 2023-01-03 · 0 comments