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
This commit is contained in:
@@ -42,8 +42,8 @@ noinline fn dummy2() void {}
|
||||
// :2:23: error: expected a tuple, found 'void'
|
||||
// :5:21: error: unable to perform 'never_inline' call at compile-time
|
||||
// :8:21: error: unable to perform 'never_tail' call at compile-time
|
||||
// :11:5: error: 'never_inline' call of inline function
|
||||
// :11:5: error: cannot perform inline call with 'never_inline' modifier
|
||||
// :15:26: error: modifier 'compile_time' requires a comptime-known function
|
||||
// :18:9: error: 'always_inline' call of noinline function
|
||||
// :21:9: error: 'always_inline' call of noinline function
|
||||
// :18:9: error: inline call of noinline function
|
||||
// :21:9: error: inline call of noinline function
|
||||
// :26:27: error: modifier 'always_inline' requires a comptime-known function
|
||||
|
||||
Reference in New Issue
Block a user