Tracking Issue for const `ControlFlow` methods requiring `const_trait_impl`
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-blocked
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(const_control_flow)]
This is a tracking issue for const ControlFlow methods where the constification depends on #143874. See also: #148738.
Public API
// core::ops::control_flow
impl<B, C> ControlFlow<B, C> {
pub const fn break_value(self) -> Option<B>
where
Self: [const] Destruct;
pub const fn map_break<T, F>(self, f: F) -> ControlFlow<T, C>
where
F: [const] FnOnce(B) -> T + [const] Destruct;
pub const fn continue_value(self) -> Option<C>
where
Self: [const] Destruct;
pub const fn map_continue<T, F>(self, f: F) -> ControlFlow<B, T>
where
F: [const] FnOnce(C) -> T + [const] Destruct;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation: #148285
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with this tracking issue, the implementation PR #148285, and the constification dependency #143874; compare the related issue #148738. Read the linked stabilization guide to understand the remaining Final Comment Period and stabilization PR steps. Done means the feature completes those lifecycle steps and the checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100