diff options
| author | bors <bors@rust-lang.org> | 2023-10-14 00:57:09 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-10-14 00:57:09 +0000 |
| commit | 75a5dd05bc53879a01f58f3503acab436ab179a5 (patch) | |
| tree | d97a08dcc9e0269e84a50b6a54a96ed058d93775 /compiler/rustc_codegen_gcc | |
| parent | fcab24817c72ffbd6ffb66d92b7ddc0d3ee4d2f0 (diff) | |
| parent | bd33846253b77ec876e130d8e010c221c80182e0 (diff) | |
| download | rust-75a5dd05bc53879a01f58f3503acab436ab179a5.tar.gz rust-75a5dd05bc53879a01f58f3503acab436ab179a5.zip | |
Auto merge of #115524 - RalfJung:misalign, r=wesleywiser
const-eval: make misalignment a hard error It's been a future-incompat error (showing up in cargo's reports) since https://github.com/rust-lang/rust/pull/104616, Rust 1.68, released in March. That should be long enough. The question for the lang team is simply -- should we move ahead with this, making const-eval alignment failures a hard error? (It turns out some of them accidentally already were hard errors since #104616. But not all so this is still a breaking change. Crater found no regression.)
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions