diff options
| author | bors <bors@rust-lang.org> | 2024-09-18 07:05:14 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-09-18 07:05:14 +0000 |
| commit | f68c28b6cefb9e1f9c258f20a3b1b7b7cddbc84f (patch) | |
| tree | 3248b65a7ab241925efc55ae3172c0a5fef70193 /compiler/rustc_parse/src/parser/diagnostics.rs | |
| parent | f6bcd094abe174a218f7cf406e75521be4199f88 (diff) | |
| parent | 18ca8bf8ee77deb13967620b1f4829f22c16dae1 (diff) | |
| download | rust-f68c28b6cefb9e1f9c258f20a3b1b7b7cddbc84f.tar.gz rust-f68c28b6cefb9e1f9c258f20a3b1b7b7cddbc84f.zip | |
Auto merge of #129845 - scottmcm:redo-layout, r=Noratrieb
Take more advantage of the `isize::MAX` limit in `Layout` Things like `padding_needed_for` are current implemented being super careful to handle things like `Layout::size` potentially being `usize::MAX`. But now that #95295 has happened, that's no longer a concern. It's possible to add two `Layout::size`s together without risking overflow now. So take advantage of that to remove a bunch of checked math that's not actually needed. For example, the round-up-and-add-next-size in `extend` doesn't need any overflow checks at all, just the final check for compatibility with the alignment. (And while I was doing that I made it all unstably const, because there's nothing in `Layout` that's fundamentally runtime-only.)
Diffstat (limited to 'compiler/rustc_parse/src/parser/diagnostics.rs')
0 files changed, 0 insertions, 0 deletions
