parser: ostensibly fix sentinel handling

I guess arrays don't need special handling because their memory is
explicitly accounted for, but it would probably be good to check that
a sentinel-terminated array initialized as `undefined` does get the
correct sentinel value.
This commit is contained in:
2023-10-22 16:38:41 -07:00
parent f371f16e2f
commit ce65dee71f
2 changed files with 18 additions and 5 deletions

View File

@@ -9,7 +9,7 @@ const Example = struct {
useful: bool,
number: i32,
string: []const u8,
longstring: []const u8,
longstring: [:0]const u8,
tuple: struct { bool, i8 },
enume: enum { first, second, third },
taggart: union(enum) { first: []const u8, second: i32 },