-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Stabilize the loop_break_value feature #42016
Stabilize the loop_break_value feature #42016
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pnkfelix (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
I think you forgot to update the tests:
|
Woops! Removed that test. |
☔ The latest upstream changes (presumably #41857) made this pull request unmergeable. Please resolve the merge conflicts. |
Seems like the reviewer is taking some time off. |
@bors r+ |
📌 Commit 93c1f24 has been approved by |
@pietroalbini thanks! Sorry for the delay, I've been traveling. This looks good though. |
⌛ Testing commit 93c1f24 with merge 5eafa87... |
💔 Test failed - status-travis |
Ugh. Something received SIGSEGV while testing the standard library I guess. Is this a random failure?
|
…alue, r=nikomatsakis Stabilize the loop_break_value feature Tracking issue: rust-lang#37339. Documentation PRs already sent to the various repositories.
Tracking issue: #37339.
Documentation PRs already sent to the various repositories.