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
538 B
Text
30 lines
538 B
Text
mutual
|
|
def f : Nat → Bool → Nat
|
|
| n, true => 2 * f n false
|
|
| 0, false => 1
|
|
| n, false => n + g n
|
|
termination_by n b => (n, if b then 2 else 1)
|
|
|
|
def g (n : Nat) : Nat :=
|
|
if h : n ≠ 0 then
|
|
f (n-1) true
|
|
else
|
|
n
|
|
termination_by (n, 0)
|
|
end
|
|
|
|
/--
|
|
info: @[irreducible] def f : Nat → Bool → Nat :=
|
|
fun a a_1 => f._mutual (PSum.inl ⟨a, a_1⟩)
|
|
-/
|
|
#guard_msgs in
|
|
#print f
|
|
|
|
/--
|
|
info: @[irreducible] def g : Nat → Nat :=
|
|
fun n => f._mutual (PSum.inr n)
|
|
-/
|
|
#guard_msgs in
|
|
#print g
|
|
|
|
#print f._mutual
|