summary refs log tree commit diff
path: root/compiler/rustc_passes/src/errors.rs
diff options
context:
space:
mode:
authorJubilee <workingjubilee@gmail.com>2024-09-09 19:20:39 -0700
committerGitHub <noreply@github.com>2024-09-09 19:20:39 -0700
commit9749a9801c5d5b5c17abcce81cf78c5010e60d1b (patch)
treee8b58a3bc15bc5f3a6cf0d7a69961ff96030523f /compiler/rustc_passes/src/errors.rs
parentca3f4ae20a59975e77552226edbb418310126fb8 (diff)
parente10224a7c3b7dbe5942e021d0b7f8230128cb9af (diff)
downloadrust-9749a9801c5d5b5c17abcce81cf78c5010e60d1b.tar.gz
rust-9749a9801c5d5b5c17abcce81cf78c5010e60d1b.zip
Rollup merge of #130164 - RalfJung:const_ptr_as_ref, r=dtolnay
move some const fn out of the const_ptr_as_ref feature

When a `const fn` is still `#[unstable]`, it should generally use the same feature to track its regular stability and const-stability. Then when that feature moves towards stabilization we can decide whether the const-ness can be stabilized as well, or whether it should be moved into a new feature.

Also, functions like `ptr::as_ref` (which returns an `Option<&mut T>`) require `is_null`, which is tricky and blocked on some design concerns (see #74939). So move those to the is_null feature gate, as they should be stabilized together with `ptr.is_null()`.

Affects #91822, #122034, #75402, https://github.com/rust-lang/rust/issues/74939
Diffstat (limited to 'compiler/rustc_passes/src/errors.rs')
0 files changed, 0 insertions, 0 deletions