Bot releases are hidden (Show)
Some notable changes in this release:
ContextPool
and ResultContextPool
now always cancels its context when Wait()
returns.ContextPool
and ResultContextPool
now cancels its context when a task panics.panics.RecoveredPanic
and panics.NewRecoveredPanic(...)
have been renamed panics.Recovered
and panics.NewRecovered(...)
respectively.panics.Recovered
no longer implements error
directly, which would previously have unintended side effects - instead, it can be converted into an error implementation explicitly with (*Recovered).AsError()
.panics.Try(...)
for recovering from panics from a single function.conc
now uses the standard library multi-error implementation
conc
now uses the go.uber.org/multierr
libraryFull changelog: https://github.com/sourcegraph/conc/compare/v0.2.0...v0.3.0
Some of the changes listed above are breaking changes - this package is currently pre-1.0, and there are likely to be other breaking changes before a 1.0 release as we stabilize the APIs and tweak defaults. Please open an issue if you have questions, concerns, or requests that you'd like addressed before the 1.0 release. Currently, a 1.0 is targeted for March 2023.
Published by bobheadxi over 1 year ago
Some notable changes in this release:
ContextPool
and ResultContextPool
no longer cancel on the first task that errors by default. To enable cancellation on first error, use WithCancelOnError
.conc.PanicCatcher
and conc.RecoveredPanic
have been moved to a new subpackage, panics
.iter.Iterator
and iter.Mapper
for configurable concurrency on ForEach
, Map
, and friends. The top-level iter.ForEach
, etc will continue to work as before.WaitGroup.WaitAndRecover
, which returns any recovered panics instead of re-panicking them.Full changelog: https://github.com/sourcegraph/conc/compare/v0.1.0...v0.2.0
Some of the changes listed above are breaking changes - this package is currently pre-1.0, and there are likely to be other breaking changes before a 1.0 release as we stabilize the APIs and tweak defaults. Please open an issue if you have questions, concerns, or requests that you'd like addressed before the 1.0 release. Currently, a 1.0 is targeted for March 2023.
Published by camdencheek almost 2 years ago