Uh oh!
There was an error while loading. Please reload this page.
Stabilize the loop_break_value feature - #42016
Conversation
rust-highfive
commented
May 15, 2017
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. |
arielb1
commented
May 16, 2017
I think you forgot to update the tests: |
emilyalbini
commented
May 16, 2017
Woops! Removed that test. |
bors
commented
May 17, 2017
☔ The latest upstream changes (presumably #41857) made this pull request unmergeable. Please resolve the merge conflicts. |
emilyalbini
commented
May 21, 2017
Seems like the reviewer is taking some time off. |
nikomatsakis
commented
May 22, 2017
@bors r+ |
bors
commented
May 22, 2017
📌 Commit 93c1f24 has been approved by |
nikomatsakis
commented
May 22, 2017
@pietroalbini thanks! Sorry for the delay, I've been traveling. This looks good though. |
bors
commented
May 22, 2017
⌛ Testing commit 93c1f24 with merge 5eafa87... |
bors
commented
May 22, 2017
💔 Test failed - status-travis |
emilyalbini
commented
May 22, 2017
Ugh. Something received SIGSEGV while testing the standard library I guess. Is this a random failure? |
Mark-Simulacrum
commented
May 22, 2017
…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.