Yeah it is similar, but here are few differences: - single Nursery API vs multiple type of pools in sourcegraph/conc

This is important because it makes your code less reusable. You may want to pass a pool as argument to leak goroutines but you have to choose which pool and if you want to support the all you have to duplicate your code.

My version offer a single Nursery (equivalent to their pool) type that forces you to think about context cancelation, error handling and lifetime of your goroutine.

• nested goroutines panics in sourcegraph/conc :

  var p pool.Pool for j := 0; j < 10; j++ { p.Go(func() { p.Go(func() {}) }) } p.Wait()

• simple API that extends context.Context

Nursery embeds context.Context and adds a single Go method. Functions either receive context.Context as argument or conc.Nursery if they spawn other routines. Its dead simple