lean4-htt/tests/lean/namedHoles.lean.expected.out
Leonardo de Moura 5d3f0606d2 feat: include type of type in "mismatch errors"
@Kha we do that in Lean 3. It helps when the error is due to incorrect universe levels.

BTW, I had to update `tests/lean/server/content_diag.json` since the
error message is different, but a few other stuff changed too.
Could you please take a look whether the test is still correct?
2021-03-08 09:30:34 -08:00

18 lines
550 B
Text

namedHoles.lean:9:7-9:14: error: application type mismatch
f ?m ?m
argument
?m
has type
Nat : Type
but is expected to have type
Bool : Type
g ?m ?m : Nat
20
foo (fun (x : Nat) => ?m x) ?m : Nat
bla ?m fun (x : Nat) => ?m : Nat
namedHoles.lean:35:38-35:43: error: synthetic hole has already been defined with an incompatible local context
boo (fun (x : Nat) => ?m x) fun (y : Bool) => sorry : Nat
11
12
namedHoles.lean:58:26-58:31: error: synthetic hole has already been defined and assigned to value incompatible with the current context
y