You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
github.com/pkg/errors The archive is no longer being updated, and std errors provides the ability to do so, so I want to remove github.com/pkg/errors and switch back to using the standard library.
What do you think? I will do this if you agree
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
std errors doesn't provide all the functionality of github.com/pkg/errors - particularly capturing a stack trace with an error. So I'd be against this for now.
From github.com/pkg/errors:
With the upcoming Go2 error proposals this package is moving into maintenance mode.
So it is maintenance mode, but waiting to be replaced by the Go2 proposal. So I would argue we shouldn't switch out until that lands.
errors has gone into read-only mode due to lack of new maintainers.
If we are currently relying on stack trace, then we can indeed wait a bit longer, as all the features have been largely implemented except for stack trace
Is your feature request related to a problem? Please describe.
github.com/pkg/errors
The archive is no longer being updated, and std errors provides the ability to do so, so I want to removegithub.com/pkg/errors
and switch back to using the standard library.What do you think? I will do this if you agree
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: