-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
For structs that cannot be unsized, the layout algorithm sometimes moves unsized fields to the end of the struct, which circumvented the error for unexpected unsized fields and returned an unsized layout anyway. This commit makes it so that the unexpected unsized error is always returned for structs that cannot be unsized, allowing us to remove an old hack and fixing some old ICE.
- Loading branch information
Lukas Markeffsky
committed
Sep 16, 2024
1 parent
07b995f
commit 4edbd93
Showing
6 changed files
with
55 additions
and
50 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
6 changes: 5 additions & 1 deletion
6
tests/crashes/127737.rs → ...s/ui/layout/invalid-unsized-const-prop.rs
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
// issue: rust-lang/rust#126939 | ||
|
||
//! This used to ICE, because the layout algorithm did not check for unsized types | ||
//! in the struct tail of always-sized types (i.e. those that cannot be unsized) | ||
//! and incorrectly returned an unsized layout. | ||
|
||
struct MySlice<T>(T); | ||
type MySliceBool = MySlice<[bool]>; | ||
|
||
struct P2 { | ||
b: MySliceBool, | ||
//~^ ERROR: the size for values of type `[bool]` cannot be known at compilation time | ||
} | ||
|
||
static CHECK: () = assert!(align_of::<P2>() == 1); | ||
|
||
fn main() {} |
23 changes: 23 additions & 0 deletions
23
tests/ui/layout/invalid-unsized-in-always-sized-tail.stderr
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
error[E0277]: the size for values of type `[bool]` cannot be known at compilation time | ||
--> $DIR/invalid-unsized-in-always-sized-tail.rs:11:8 | ||
| | ||
LL | b: MySliceBool, | ||
| ^^^^^^^^^^^ doesn't have a size known at compile-time | ||
| | ||
= help: the trait `Sized` is not implemented for `[bool]` | ||
note: required by an implicit `Sized` bound in `MySlice` | ||
--> $DIR/invalid-unsized-in-always-sized-tail.rs:7:16 | ||
| | ||
LL | struct MySlice<T>(T); | ||
| ^ required by the implicit `Sized` requirement on this type parameter in `MySlice` | ||
help: you could relax the implicit `Sized` bound on `T` if it were used through indirection like `&T` or `Box<T>` | ||
--> $DIR/invalid-unsized-in-always-sized-tail.rs:7:16 | ||
| | ||
LL | struct MySlice<T>(T); | ||
| ^ - ...if indirection were used here: `Box<T>` | ||
| | | ||
| this could be changed to `T: ?Sized`... | ||
|
||
error: aborting due to 1 previous error | ||
|
||
For more information about this error, try `rustc --explain E0277`. |