diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-11-16 21:05:44 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-16 21:05:44 +0100 |
| commit | fb5bd7ffcc0563f9fed8a0a586e973f9c44124bf (patch) | |
| tree | 742ab0ae12848e9d52283c5378c0f345e60c850e /compiler/rustc_codegen_gcc/example/alloc_system.rs | |
| parent | 5c81dbf4fa8b8d39e55e46c49864589724bb28fe (diff) | |
| parent | 7651fc6edc5c838f955f881b5e93a7d669549940 (diff) | |
| download | rust-fb5bd7ffcc0563f9fed8a0a586e973f9c44124bf.tar.gz rust-fb5bd7ffcc0563f9fed8a0a586e973f9c44124bf.zip | |
Rollup merge of #132449 - RalfJung:is_val_statically_known, r=compiler-errors
mark is_val_statically_known intrinsic as stably const-callable The intrinsic doesn't actually "do" anything in terms of language semantics, and we are already using it in stable const fn. So let's just properly mark it as stably const-callable to avoid needing `rustc_allow_const_fn_unstable` (and thus reducing noise and keeping the remaining `rustc_allow_const_fn_unstable` as a more clear signal). Cc `@rust-lang/lang` usually you have to approve exposing intrinsics in const, but this intrinsic is basically just a compiler implementation detail. So FCP doesn't seem necessary. Cc `@rust-lang/wg-const-eval`
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_system.rs')
0 files changed, 0 insertions, 0 deletions