Fix gap in const stability checks around intrinsics - #162409
Conversation
|
cc @rust-lang/wg-const-eval Some changes occurred to constck cc @fee1-dead Some changes occurred to the CTFE machinery Some changes occurred to the intrinsics. Make sure the CTFE / Miri interpreter |
|
r? @mati865 rustbot has assigned @mati865. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
sorry about that 😓 |
2d64547 to
bc0851a
Compare
It was me who introduced this bug, you just found it. ;) |
bc0851a to
b3a8050
Compare
This comment has been minimized.
This comment has been minimized.
b3a8050 to
9d60be8
Compare
This comment has been minimized.
This comment has been minimized.
9d60be8 to
022d14a
Compare
| #[rustc_intrinsic_const_stable_indirect] | ||
| #[rustc_intrinsic] | ||
| #[miri::intrinsic_fallback_is_spec] | ||
| #[rustc_allow_const_fn_unstable(const_ops, const_trait_impl, core_intrinsics)] // FIXME these got accidentally exposed |
There was a problem hiding this comment.
The interpreter has an implementation for this, right? So we can just use do_not_const_check.
022d14a to
4896f11
Compare
4896f11 to
64752fb
Compare
@N1ark managed to find a gap in our const stability checks around intrinsics. This PR fixes that gap.
Sadly the standard library already relies on the gap, so for now I added a
rustc_allow_const_fn_unstablebut that attribute usually needs some process to be approved.