@Sebastien The biggest difference is my package makes guarantees that when a bundle is garbage collected the context and thus child goroutines are cancelled. This lets you be more creative having shared ownership of groups of goroutines, e.g. a collection of goroutines producing a lazy infinite series on a channel, which would be safely closed once all references to the bundle are gone.
errgroup seem to have a 'heavier' api, focused on aggregating errors, It also seems strange to me that the 'group' function in errgroup does not accept a context which is idiomatic go. Being biased, I prefer my own API, but actually, use whichever you prefer :) -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
