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
Proposal: errors: merge github.com/pkg/errors #16968
Comments
I very much like @davecheney's const error suggestion ( I'm not sure I would care for Errorf gathering a stack trace. It's handy in some situations, that seems like unnecessary overhead for the general case. Perhaps I just do not see what benefits this provides. It seems more like a debugging tool, imo. |
You seem to have answered your own question. It is a debugging tool, and that is the benefit it provides. |
@SamWhited sorry, I wasn't as clear as I should've been. I do not see what benefits this provides for the errors package the way the it is currently structured. I wouldn't mind something like |
As @davecheney said (https://twitter.com/davecheney/status/771688315573579778), the bar to entry for the standard library is very high. I would ask for Dave to write a more formal design document and enter the proposal process, but I can say at this point that the likelihood of this happening is close to zero. I agree we should do something more about errors, but it's more of a Go2 item. I'm going to close this for now. |
Related to #15192 |
Agreed. On Tue, Oct 25, 2016 at 9:16 AM, Brad Fitzpatrick notifications@github.com
|
I think that the API suggested by @davecheney in his GopherContalk and implemented in the repo github.com/pkg/errors should be integrated into the errors package of the standard lib.
I learned that this is already his plan [1], but failed to find an issue or proposal here to track the progress, hence I created this one.
[1] https://twitter.com/davecheney/status/771688315573579778
The text was updated successfully, but these errors were encountered: