-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Bury Error::description() #50163
Bury Error::description() #50163
Conversation
r? @Kimundi (rust_highfive has picked a reviewer for you, use r? to override) |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Seems fine, I'll r+ as soon as the tests pass. |
… rather than the module’s. Remove code definition of the Error trait from its doc-comment It was out of date, and rustdoc already shows the same information. Add a default impl for Error::description and document it as deprecated. It is redundant with Display while being much less flexible for implementors. This is only a "soft" deprecation: it is not worth the hassle of a warning to existing users. Tweak Error trait docs to reflect actual requirements
It passes the tests now |
Ping from triage @Kimundi! The tests are passing now. |
@bors r+ |
📌 Commit 1912f39 has been approved by |
Bury Error::description() Second attempt of #49536 rust-lang/rfcs#2230 The exact wording of the default implementation is still up in the air, but I think it's a detail that can be amended later.
☀️ Test successful - status-appveyor, status-travis |
Deprecated since Rust 1.42.0, but does not require 1.42.0, because deprecation has been prepared in rust-lang/rust#50163 by providing a default implementation.
Second attempt of #49536 rust-lang/rfcs#2230
The exact wording of the default implementation is still up in the air, but I think it's a detail that can be amended later.