about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/context.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-11-01 19:07:57 +0000
committerbors <bors@rust-lang.org>2024-11-01 19:07:57 +0000
commit705cfe0e966399e061d64dd3661bfbc57553ed87 (patch)
treee1ed1ba9179895f4aa6c9c2a7b1cef8d5626242a /compiler/rustc_codegen_llvm/src/context.rs
parent5ca0e9fa9b2f92b463a0a2b0b34315e09c0b7236 (diff)
parent57f2e12f4aafb2c37f45090be97c68c5020c938f (diff)
downloadrust-705cfe0e966399e061d64dd3661bfbc57553ed87.tar.gz
rust-705cfe0e966399e061d64dd3661bfbc57553ed87.zip
Auto merge of #132276 - compiler-errors:enforce-fx-in-mir, r=fee1-dead
Double-check conditional constness in MIR

To prevent any unchecked `~const` bounds from leaking through during MIR lowering.

If this check fails, it will eventually just delay a bug, but for now it reports errors. That error reporting may be redundant if we're calling it from code that already doesn't allow `~const` (i.e. when the `effects` and `const_trait_impl` gates are disabled), but I don't think it's that big of a deal.

edit: This also makes sure that we issue a const stability error if we encounter *any* function with const conditions when `const_trait_impl` is not enabled. This ensures that that feature remains airtight.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/context.rs')
0 files changed, 0 insertions, 0 deletions