-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Add the try_trait_v2
library basics
#84092
Conversation
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
No compiler changes as part of this -- just new unstable traits and impls thereof. The goal here is to add the things that aren't going to break anything, to keep the feature implementation simpler in the next PR.
7b32024
to
1864970
Compare
Updated with a real tracking issue, now that the RFC is merged, so I think this is good to go now. (Sorry for not ghosting it previously.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very exciting!
/// But this "call `branch`, then `match` on it, and `return` if it was a | ||
/// `Break`" is exactly what happens inside the `?` operator. So rather than | ||
/// do all this manually, we can just use `?` instead: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oooo this is soo satisfying.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This PR looks good to me. I would like to see a bullet point on further planned documentation updates recorded somewhere, presumably on the tracking issue. |
It had the standard "adjust documentation" checkbox, but that's often more about the reference and such, so I've added another one for more library documentation in #84277. |
Since the RFC has merged am I right in assuming this is ready to merge now? |
yolo @rfcbot merge |
Team member @yaahc has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), 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. |
As this is all unstable I don't think it needs an FCP? It should be entirely invisible to stable code. (Shouldn't impact any unstable code either, since it's just additions. The next PR that will change the bounds on iterator methods and such might need more eyes on it, but the goal for this PR was to not have to.) |
Looks great to me! Also verified that this only adds unstable things and has no effect on existing code. @bors r=yaahc,m-ou-se |
📌 Commit 5671647 has been approved by |
☀️ Test successful - checks-actions |
No compiler changes as part of this -- just new unstable traits and impls thereof.
The goal here is to add the things that aren't going to break anything, to keep the feature implementation simpler in the next PR.
(Draft since the FCP won't end until Saturday, but I was feeling optimistic today -- and had forgotten that FCP was 10 days, not 7 days.)