Alejandro Durante

Hey @mylxy! The value reported by `pool.RunningWorkers()` is the number of worker gorutines that is currently running (either executing a task or idle), so it won't necessarily match the total...

`pool.RunningWorkers()` reflects the total number of worker goroutines that are running (either busy or idle), while `pool.IdleWorkers()` only returns the number of worker goroutines that are not currently processing any...

Hey @kdonthi! Yes, panics are probably not the best way to handle all application errors, but I think it's important to distinguish between two general kinds of errors: - **Recoverable...

Hey @koenbok! I'm afraid nested groups will not work with that setup, since it's reusing the same worker pool for both group levels (A and B). Each worker pool receives...

Hey @Kaszanas! ## Unlimited task queues This library doesn't currently have support for setting up unlimited task queues. This was an intentional design decision for the sake of simplicity and...

Hi @mikegleasonjr! Yes, the behaviour you are describing is correct and it's by design. Unlike the `StopAndWait()` method on the worker pool, the context group's `Wait()` method waits until either...

Hey @mikegleasonjr I wanted to let you know v2 of this library now comes with a new kind of pool that could be useful in this particular use case. You...

Hey @pkovacs, I'd like to know more about that use case, could you share a pseudo-code snippet of what your tree of tasks looks like? In `v2`, if you need...

What do you think about this example? ```go package main import ( "context" "fmt" "github.com/alitto/pond/v2" ) var pool pond.Pool type Task struct { n int } type SubTask struct {...

I'm glad You find it useful! 🙂 Cheers