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/typename.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/typename.zig')
| -rw-r--r-- | test/behavior/typename.zig | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/behavior/typename.zig b/test/behavior/typename.zig index 6682b99f4d..79de5fd442 100644 --- a/test/behavior/typename.zig +++ b/test/behavior/typename.zig @@ -238,7 +238,7 @@ test "comptime parameters not converted to anytype in function type" { if (builtin.zig_backend == .stage2_arm) return error.SkipZigTest; // TODO if (builtin.zig_backend == .stage2_sparc64) return error.SkipZigTest; // TODO - const T = fn (fn (type) void, void) void; + const T = fn (comptime fn (comptime type) void, void) void; try expectEqualStrings("fn (comptime fn (comptime type) void, void) void", @typeName(T)); } |