diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-08-24 22:14:12 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-24 22:14:12 +0200 |
| commit | 05b8bcc662afcfa9d3ccbe2dd0f48113fd1fb224 (patch) | |
| tree | 6349421f6b305fb03c47eea293c6e48201f06c61 /compiler/rustc_ast_lowering/src/asm.rs | |
| parent | 0dfdea1c45b1b832391cb32db0fd58d0ec29d967 (diff) | |
| parent | 8b642a1883c489c74befca5b75514767a1f80314 (diff) | |
| download | rust-05b8bcc662afcfa9d3ccbe2dd0f48113fd1fb224.tar.gz rust-05b8bcc662afcfa9d3ccbe2dd0f48113fd1fb224.zip | |
Rollup merge of #129199 - RalfJung:writes_through_immutable_pointer, r=compiler-errors
make writes_through_immutable_pointer a hard error This turns the lint added in https://github.com/rust-lang/rust/pull/118324 into a hard error. This has been reported in cargo's future-compat reports since Rust 1.76 (released in February). Given that const_mut_refs is still unstable, it should be impossible to even hit this error on stable: we did accidentally stabilize some functions that can cause this error, but that got reverted in https://github.com/rust-lang/rust/pull/117905. Still, let's do a crater run just to be sure. Given that this should only affect unstable code, I don't think it needs an FCP, but let's Cc ``@rust-lang/lang`` anyway -- any objection to making this unambiguous UB into a hard error during const-eval? This can be viewed as part of https://github.com/rust-lang/rust/pull/129195 which is already nominated for discussion.
Diffstat (limited to 'compiler/rustc_ast_lowering/src/asm.rs')
0 files changed, 0 insertions, 0 deletions