Proposal Details
See https://github.com/golang/go/issues/74304#issue-3160794178 and https://github.com/golang/go/issues/53757#issuecomment-2988592157 , Sometimes we need to restore the old behavior of errgroup, and I suggest adding a new field Propagate to achieve this, turning the new behavior into an option to join.
Don't use GODEBUG because don't know what to set its default value and what to enable new behavior when the go line in go.mod changes to.
I can send CL implement this proposal.
open-ended question: Do we also need to adopt https://go.dev/cl/682335 or #74275 for faster panic when using new behaviors?
Comment From: gabyhelp
Related Issues
- proposal: x/sync/errgroup: propagate panics through Go #74275
- proposal: x/sync/errgroup: optionally collect all errors #72101 (closed)
(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)
Comment From: seankhliao
It sounds like in #53757 that we should just revert it and allow crashes to happen. Should we close this?
Comment From: adonovan
It sounds like in https://github.com/golang/go/issues/53757 that we should just revert it and allow crashes to happen. Should we close this?
I think so, yes. Users of errgroup can already implement the semantics they want on top of errgroup.
Comment From: gopherbot
Change https://go.dev/cl/682935 mentions this issue: errgroup: revert propagation of panics