995fa4766b
This PR refines the new wording of the "application type mismatch" error message to avoid ambiguity in references to the "final" argument in a subexpression that may be followed by additional arguments. It does so by replacing "final" with "last," rephrasing the message so that this adjective modifies the argument itself rather than the word "argument," and only displaying this wording when two arguments could be confused (determined by expression equality). These changes were motivated by a report that in cases where a function application `f a b c` fails to elaborate because `b` is incorrectly typed, the existing error message's reference to `b` being the "final" argument in the application `f a b` may create confusion because it is not the final argument in the full application expression.
20 lines
449 B
Text
20 lines
449 B
Text
doIssue.lean:2:2-2:3: error: type mismatch
|
|
x
|
|
has type
|
|
Nat : Type
|
|
but is expected to have type
|
|
IO PUnit : Type
|
|
doIssue.lean:10:2-10:13: error: type mismatch
|
|
xs.set! 0 1
|
|
has type
|
|
Array Nat : Type
|
|
but is expected to have type
|
|
IO PUnit : Type
|
|
doIssue.lean:18:7-18:20: error: Application type mismatch: In the application
|
|
pure (xs.set! 0 1)
|
|
the argument
|
|
xs.set! 0 1
|
|
has type
|
|
Array Nat : Type
|
|
but is expected to have type
|
|
PUnit : Type
|