Closed
Description
openedon Mar 18, 2018
This is a tracking issue for the RFC "Allow if and match in constants" (rust-lang/rfcs#2342).
Please redirect constification of specific functions or issues you want to report to fresh issues and label them appropriately with F-const_if_match so that this issues doesn't get flooded with ephemeral comments obscuring important developments.
Steps:
- Implement the RFC
- Adjust documentation (see instructions on forge)
- Stabilization PR (see instructions on forge): Stabilize
#![feature(const_if_match)]and#![feature(const_loop)]#72437 -
letbindings in constants that use&&and||short circuiting operations. These are treated as&and|insideconstandstaticitems right now.
Unresolved questions:
None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Area: Constant evaluation (MIR interpretation)Area: const fn foo(..) {..}. Pure functions which can be applied at compile time.Blocker: Approved by a merged RFC but not yet implemented.Category: A tracking issue for an RFC or an unstable feature.Relevant to the language team, which will review and decide on the PR/issue.This issue / PR is in PFCP or FCP with a disposition to merge it.The final comment period is finished for this PR / Issue.