diff options
| author | mlugg <mlugg@mlugg.co.uk> | 2025-01-05 05:27:48 +0000 |
|---|---|---|
| committer | mlugg <mlugg@mlugg.co.uk> | 2025-01-09 06:46:47 +0000 |
| commit | e9bd2d45d4bbaf7eff7e95bc3ef7a0123b66a103 (patch) | |
| tree | da18bc40935c7dd9698d792eae3d102fa0ad67ae /test/behavior/struct.zig | |
| parent | 3f95003d4c57650f9b4779f55c8d7368b137337c (diff) | |
| download | zig-e9bd2d45d4bbaf7eff7e95bc3ef7a0123b66a103.tar.gz zig-e9bd2d45d4bbaf7eff7e95bc3ef7a0123b66a103.zip | |
Sema: rewrite semantic analysis of function calls
This rewrite improves some error messages, hugely simplifies the logic,
and fixes several bugs. One of these bugs is technically a new rule
which Andrew and I agreed on: if a parameter has a comptime-only type
but is not declared `comptime`, then the corresponding call argument
should not be *evaluated* at comptime; only resolved. Implementing this
required changing how function types work a little, which in turn
required allowing a new kind of function coercion for some generic use
cases: function coercions are now allowed to implicitly *remove*
`comptime` annotations from parameters with comptime-only types. This is
okay because removing the annotation affects only the call site.
Resolves: #22262
Diffstat (limited to 'test/behavior/struct.zig')
| -rw-r--r-- | test/behavior/struct.zig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/behavior/struct.zig b/test/behavior/struct.zig index b45fa171cb..1ba81695b8 100644 --- a/test/behavior/struct.zig +++ b/test/behavior/struct.zig @@ -1511,7 +1511,7 @@ test "if inside struct init inside if" { test "optional generic function label struct field" { const Options = struct { - isFoo: ?fn (type) u8 = defaultIsFoo, + isFoo: ?fn (comptime type) u8 = defaultIsFoo, fn defaultIsFoo(comptime _: type) u8 { return 123; } |