8424ddbb3e
This PR improves the “expected type mismatch” error message by omitting the type's types when they are defeq, and putting them into separate lines when not. I found it rather tediuos to parse the error message when the expected type is long, because I had to find the `:` in the middle of a large expression somewhere. Also, when both are of sort `Prop` or `Type` it doesn't add much value to print the sort (and it’s only one hover away anyways).
20 lines
407 B
Text
20 lines
407 B
Text
doIssue.lean:2:2-2:3: error: type mismatch
|
|
x
|
|
has type
|
|
Nat
|
|
but is expected to have type
|
|
IO PUnit
|
|
doIssue.lean:10:2-10:13: error: type mismatch
|
|
xs.set! 0 1
|
|
has type
|
|
Array Nat
|
|
but is expected to have type
|
|
IO PUnit
|
|
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
|
|
but is expected to have type
|
|
PUnit
|