lean4-htt/tests/lean/nameArgErrorIssue.lean.expected.out
jrr6 995fa4766b
fix: reduce ambiguity of "final" in application type mismatch message (#8322)
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.
2025-05-14 16:12:10 +00:00

20 lines
574 B
Text

bla 5 2 : Nat
nameArgErrorIssue.lean:5:20-5:24: error: Application type mismatch: In the application
bla "hi"
the argument
"hi"
has type
String : Type
but is expected to have type
Nat : Type
bla sorry 5 : Nat
nameArgErrorIssue.lean:6:20-6:24: error: Application type mismatch: In the application
bla "hi"
the argument
"hi"
has type
String : Type
but is expected to have type
Nat : Type
nameArgErrorIssue.lean:6:11-6:19: error: invalid argument name 'z' for function 'bla'
nameArgErrorIssue.lean:7:11-7:19: error: invalid argument name 'z' for function 'bla'