const-features can be both stable and unstable at the same time #91357
Labels
A-const-eval
Area: Constant evaluation (MIR interpretation)
A-const-fn
Area: const fn foo(..) {..}. Pure functions which can be applied at compile time.
A-stability
Area: `#[stable]`, `#[unstable]` etc.
C-bug
Category: This is a bug.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Since #90896, the
const_maybe_uninit_assume_init
feature is in a strange limbo state: there are both stable and unstable methods with that feature gate. For regular stability we prevent that, but it seems for const-stability that check is missing.Cc @rust-lang/wg-const-eval
The text was updated successfully, but these errors were encountered: