Closed
Description
RFC.
Current status:
- Implemented.Decided to stabilize.Documentation PR: Feature/loop break value reference#56 (See final section of the Rust Forge stabilization instructions for advice.)Stabilization PR: Stabilize the loop_break_value feature #42016 (See the Rust Forge for instructions.)
Metadata
Metadata
Assignees
Labels
Blocker: Approved by a merged RFC but not yet implemented.Blocker: Implemented in the nightly compiler and unstable.Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.Call for participation: This issue has a mentor. Use #t-compiler/help on Zulip for discussion.Relevant to the language teamIn the final comment period and will be merged soon unless new substantive objections are raised.
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
aturon commentedon Oct 22, 2016
Currently awaiting implementation.
cc @dhardy
eddyb commentedon Oct 22, 2016
@aturon How would we go about advertising mentorship? If someone wants to implement this and they're not already familiar with the compiler internals, they can come to
#rustc
on IRC to discuss it.This is the case for many such features with a relatively small footprint, we're glad to help.
(Although I may be spreading myself thin a bit too much instead of finishing my own refactors.)
aturon commentedon Oct 22, 2016
@eddyb An important question we don't have a systematic answer for right now (cc @brson). We should probably move this to an internals thread or something, though.
dhardy commentedon Oct 24, 2016
I hear you @aturon but don't have the time just now (and maybe for a few weeks).
loop_break_value
feature. #3748759 remaining items