Skip to content

Tracking Issue for const ControlFlow methods requiring const_trait_impl #148739

@nxsaken

Description

@nxsaken

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.)

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-blockedStatus: This tracking issue is blocked on another tracking issueT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions