-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go 1.20: Errors() should support any multi-error #70
Comments
Internal Ref: GO-1883 |
sywhang
added a commit
that referenced
this issue
Mar 14, 2023
Starting Go 1.20, any multi-error should conform to the standard unwrap method: Unwrap() []error. This changes multierr.Errors() method to support any error that complies to that interface. Fix #70.
sywhang
added a commit
that referenced
this issue
Mar 14, 2023
Starting Go 1.20, any multi-error should conform to the standard unwrap method: Unwrap() []error. This changes multierr.Errors() method to support any error that complies to that interface. Fix #70.
sywhang
added a commit
that referenced
this issue
Mar 16, 2023
Starting Go 1.20, any multi-error should conform to the standard unwrap method: Unwrap() []error. This changes multierr.Errors() method to support any error that complies to that interface. Fix #70 / GO-1883
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow up to #69
Now that the interface for errors wrapping multiple errors has been standardized to,
Unwrap() []error
, themultierr.Errors(error) []error
function should support any error that conforms to it, not just its own error type.This behavior should be gated behind the go1.20 build tag.
The text was updated successfully, but these errors were encountered: