lean4-htt/tests/elab/coeIssue2.lean
Garmelon 08eb78a5b2
chore: switch to new test/bench suite (#12590)
This PR sets up the new integrated test/bench suite. It then migrates
all benchmarks and some related tests to the new suite. There's also
some documentation and some linting.

For now, a lot of the old tests are left alone so this PR doesn't become
even larger than it already is. Eventually, all tests should be migrated
to the new suite though so there isn't a confusing mix of two systems.
2026-02-25 13:51:53 +00:00

36 lines
830 B
Text
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

structure A :=
(a : Nat)
structure B :=
(a : Nat)
structure C :=
(a : Nat)
instance : Coe A B := ⟨fun s => ⟨s.1⟩⟩
instance : Coe A C := ⟨fun s => ⟨s.1⟩⟩
def f {α} (a b : α) := a
def forceB {α} (b : B) (a : α) := a
def forceC {α} (c : C) (a : α) := a
def forceA {α} (a : A) (o : α) := o
def f1 (x : _) (y : _) (z : _) :=
let a1 := f x y;
let a2 := f y z;
forceB x a1 -- works
def f2 (x : _) (y : _) (z : _) :=
let a1 := f x ↑y;
let a2 := f ↑y z;
forceB x (forceC z (forceA y (a1, a2))) -- works because we manually added the coercions above
#exit
def f3 (x : _) (y : _) (z : _) :=
let a1 := f x y;
let a2 := f y z;
/- Fails because we "missed" the opportunity to insert coercions around `y`.
I think we should **not** support this kind of example. -/
forceB x (forceC z (forceA y (a1, a2)))