Skip to content

Tracking Issue for minimal const ControlFlow methods (min_const_control_flow) #148738

@nxsaken

Description

@nxsaken

Feature gate: #![feature(min_const_control_flow)]

This is a tracking issue for the minimal constification of ControlFlow methods. Minimal means these methods can be constified without #143874 (see #148739).

Public API

// core::ops::control_flow

impl<B, C> ControlFlow<B, C> {
    pub const fn is_break(&self) -> bool;
    pub const fn is_continue(&self) -> bool;
    pub const fn break_ok(self) -> Result<B, C>;
    pub const fn continue_ok(self) -> Result<C, B>;
}

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-unimplementedStatus: The feature has not been implemented.T-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