mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
10b08e3c9c
rust/tests/ui/async-await/future-sizes/large-arg.stdout

61 lines
4.0 KiB
Plaintext
Raw Normal View History

Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `[async fn body@$DIR/large-arg.rs:6:21: 8:2]`: 3076 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size discriminant: 1 bytes
Sort Generator `print-type-sizes` according to their yield points Especially when trying to diagnose runaway future sizes, it might be more intuitive to sort the variants according to the control flow (aka their yield points) rather than the size of the variants.
2023-02-05 09:26:51 -06:00
print-type-size variant `Unresumed`: 0 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Suspend0`: 3075 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size local `.__awaitee`: 3075 bytes, offset: 0 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Returned`: 0 bytes
print-type-size variant `Panicked`: 0 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `[async fn body@$DIR/large-arg.rs:10:30: 12:2]`: 3075 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size discriminant: 1 bytes
Sort Generator `print-type-sizes` according to their yield points Especially when trying to diagnose runaway future sizes, it might be more intuitive to sort the variants according to the control flow (aka their yield points) rather than the size of the variants.
2023-02-05 09:26:51 -06:00
print-type-size variant `Unresumed`: 1024 bytes
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Suspend0`: 3074 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
print-type-size local `.__awaitee`: 2050 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Returned`: 1024 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Panicked`: 1024 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `std::mem::ManuallyDrop<[async fn body@$DIR/large-arg.rs:10:30: 12:2]>`: 3075 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size field `.value`: 3075 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `std::mem::MaybeUninit<[async fn body@$DIR/large-arg.rs:10:30: 12:2]>`: 3075 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `MaybeUninit`: 3075 bytes
print-type-size field `.uninit`: 0 bytes
print-type-size field `.value`: 3075 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `[async fn body@$DIR/large-arg.rs:13:26: 15:2]`: 2050 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size discriminant: 1 bytes
Sort Generator `print-type-sizes` according to their yield points Especially when trying to diagnose runaway future sizes, it might be more intuitive to sort the variants according to the control flow (aka their yield points) rather than the size of the variants.
2023-02-05 09:26:51 -06:00
print-type-size variant `Unresumed`: 1024 bytes
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Suspend0`: 2049 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
print-type-size local `.__awaitee`: 1025 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Returned`: 1024 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Panicked`: 1024 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `std::mem::ManuallyDrop<[async fn body@$DIR/large-arg.rs:13:26: 15:2]>`: 2050 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size field `.value`: 2050 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `std::mem::MaybeUninit<[async fn body@$DIR/large-arg.rs:13:26: 15:2]>`: 2050 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `MaybeUninit`: 2050 bytes
print-type-size field `.uninit`: 0 bytes
print-type-size field `.value`: 2050 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `[async fn body@$DIR/large-arg.rs:16:26: 18:2]`: 1025 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size discriminant: 1 bytes
print-type-size variant `Unresumed`: 1024 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Returned`: 1024 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `Panicked`: 1024 bytes
Bless tests after rebase
2023-02-01 19:38:14 -06:00
print-type-size upvar `.t`: 1024 bytes, offset: 0 bytes, alignment: 1 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `std::mem::ManuallyDrop<[async fn body@$DIR/large-arg.rs:16:26: 18:2]>`: 1025 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size field `.value`: 1025 bytes
Move ignore-pass to large-arg test
2023-01-31 12:56:55 -06:00
print-type-size type: `std::mem::MaybeUninit<[async fn body@$DIR/large-arg.rs:16:26: 18:2]>`: 1025 bytes, alignment: 1 bytes
Add tests to assert current behavior of large future sizes Based on a couple of sources: - https://swatinem.de/blog/future-size/ - https://github.com/rust-lang/rust/issues/62958
2023-01-30 21:49:11 -06:00
print-type-size variant `MaybeUninit`: 1025 bytes
print-type-size field `.uninit`: 0 bytes
print-type-size field `.value`: 1025 bytes
print-type-size type: `std::task::Poll<[u8; 1024]>`: 1025 bytes, alignment: 1 bytes
print-type-size discriminant: 1 bytes
print-type-size variant `Ready`: 1024 bytes
print-type-size field `.0`: 1024 bytes
print-type-size variant `Pending`: 0 bytes
Reference in New Issue Copy Permalink