mirror of
https://github.com/ziglang/zig.git
synced 2025-12-06 06:13:07 +00:00
7d54c62c8a
I don't recall why I put these checks here -- they aren't correct. We can freely recreate a type even if its fields have changed, because we are going to re-do all type resolution. The only conditions for recreations are (a) the ZIR index must not be lost and (b) the number of captures must be the same. These conditions are permissible because if either is violated, we can guarantee that analysis of a valid `zirStructDecl` (etc) will never reference this type (since the ZIR index has just been tracked, and the captures have just been created based on the ZIR). Adds a corresponding test case. Resolves: #21185
24 lines
520 B
Plaintext
24 lines
520 B
Plaintext
#target=x86_64-linux
|
|
#update=initial version
|
|
#file=main.zig
|
|
const MyEnum = enum(u8) {
|
|
foo = 1,
|
|
bar = 2,
|
|
};
|
|
pub fn main() !void {
|
|
try std.io.getStdOut().writer().print("{}\n", .{@intFromEnum(MyEnum.foo)});
|
|
}
|
|
const std = @import("std");
|
|
#expect_stdout="1\n"
|
|
#update=remove enum field
|
|
#file=main.zig
|
|
const MyEnum = enum(u8) {
|
|
//foo = 1,
|
|
bar = 2,
|
|
};
|
|
pub fn main() !void {
|
|
try std.io.getStdOut().writer().print("{}\n", .{@intFromEnum(MyEnum.foo)});
|
|
}
|
|
const std = @import("std");
|
|
#expect_error=ignored
|