-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Add Error::source method per RFC 2504. #53533
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
@rfcbot fcp merge Tracking issue #53487 RFC rust-lang/rfcs#2504 |
Team member @withoutboats has proposed to merge this. The next step is review by the rest of the tagged teams: No concerns currently listed. Once a majority of reviewers approve (and none object), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
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 |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
Code-wise change looks fine to me. |
@bors delegate+ |
✌️ @withoutboats can now approve this pull request |
The final comment period, with a disposition to merge, as per the review above, is now complete. |
@bors r+ |
📌 Commit e2e4f57 has been approved by |
⌛ Testing commit e2e4f57 with merge 328565efd875a4949bdcfc2d4ecc55a97d796648... |
💔 Test failed - status-travis |
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 |
@bors retry The linker is killed with SIGILL. The error doesn't seem relevant at all. |
Add Error::source method per RFC 2504. This implements part of RFC 2504. * Adds `Error::source`, a replacement for `Error::cause` with the "right" signature, which will be instantly stable. * Deprecates `Error::cause` in 1.33 (this choice was based on the precedent in #52994, which we haven't finalized). * Redefines `Error::cause` to delegate to `Error::source` (the delegation can only go in this direction, not the other). @rfcbot fcp merge
☀️ Test successful - status-appveyor, status-travis |
This implements part of RFC 2504.
Error::source
, a replacement forError::cause
with the "right" signature, which will be instantly stable.Error::cause
in 1.33 (this choice was based on the precedent in Add trim_start, trim_end etc.; deprecate trim_left, trim_right, etc. in future #52994, which we haven't finalized).Error::cause
to delegate toError::source
(the delegation can only go in this direction, not the other).@rfcbot fcp merge