diff options
| author | Cody Tapscott <topolarity@tapscott.me> | 2022-03-15 14:00:33 -0700 |
|---|---|---|
| committer | Andrew Kelley <andrew@ziglang.org> | 2022-03-15 17:01:16 -0700 |
| commit | 480e7eec65c02952b71ecc2f4ff2adccb6092a5f (patch) | |
| tree | b3637be2086b25649d71e2d24d334aa634e87e03 /test/behavior/struct.zig | |
| parent | 762c4a876bfa999d5f49edc7bbaf2917c06d320d (diff) | |
| download | zig-480e7eec65c02952b71ecc2f4ff2adccb6092a5f.tar.gz zig-480e7eec65c02952b71ecc2f4ff2adccb6092a5f.zip | |
stage2: Fix panic on initializing comptime fields in tuple
This resolves https://github.com/ziglang/zig/issues/11159
The problem was that:
1. We were not correctly deleting the field stores after recognizing
that an array initializer was a comptime-known value.
2. LLVM was not checking that the final type had no runtime bits, and
so would generate an invalid store.
This also adds several test cases for related bugs, just to check these
in for later work.
Diffstat (limited to 'test/behavior/struct.zig')
0 files changed, 0 insertions, 0 deletions