Many of our tests in `tests/lean/run/` produce output from `#eval` (or `#check`) statements, that is then ignored. This PR tries to capture all the useful output using `#guard_msgs`. I've only done a cursory check that the output is still sane --- there is a chance that some "unchecked" tests have already accumulated regressions and this just cements them! In the other direction, I did identify two rotten tests: * a minor one in `setStructInstNotation.lean`, where a comment says `Set Nat`, but `#check` actually prints `?_`. Weird? * `CompilerProbe.lean` is generating empty output, apparently indicating that something is broken, but I don't know the signficance of this file. In any case, I'll ask about these elsewhere. (This started by noticing that a recent `grind` test file had an untested `trace_state`, and then got carried away.)
30 lines
811 B
Text
30 lines
811 B
Text
inductive FinInt: Nat → Type :=
|
||
| nil: FinInt 0
|
||
| next: Bool → FinInt n → FinInt (n+1)
|
||
deriving DecidableEq
|
||
|
||
def zero (sz: Nat): FinInt sz :=
|
||
match sz with
|
||
| 0 => .nil
|
||
| sz+1 => .next false (zero sz)
|
||
|
||
inductive Pair :=
|
||
| mk (sz: Nat) (lhs rhs: FinInt sz)
|
||
|
||
def makePair?: (n m: (sz: Nat) × FinInt sz) → Option Pair
|
||
| ⟨sz, lhs⟩, ⟨sz', rhs⟩ =>
|
||
if EQ: true /\ sz = sz' then
|
||
have rhs' : FinInt sz := by {
|
||
cases EQ;
|
||
case intro left right =>
|
||
simp [right];
|
||
exact rhs;
|
||
};
|
||
some (Pair.mk sz lhs rhs')
|
||
else none
|
||
|
||
def usePair: Pair → Bool := fun ⟨sz, lhs, rhs⟩ => lhs = rhs
|
||
|
||
/-- info: some true -/
|
||
#guard_msgs in
|
||
#eval (makePair? ⟨8, zero 8⟩ ⟨8, zero 8⟩).map usePair
|