3a457e6ad6
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.)
29 lines
490 B
Text
29 lines
490 B
Text
namespace Ex1
|
|
mutual
|
|
def isEven : Nat → Bool
|
|
| 0 => true
|
|
| n+1 => isOdd n
|
|
termination_by n => n
|
|
def isOdd : Nat → Bool
|
|
| 0 => false
|
|
| n+1 => isEven n
|
|
termination_by n => n
|
|
end
|
|
|
|
/--
|
|
info: @[irreducible] def Ex1.isEven : Nat → Bool :=
|
|
fun a => isEven._mutual (PSum.inl a)
|
|
-/
|
|
#guard_msgs in
|
|
#print isEven
|
|
|
|
/--
|
|
info: @[irreducible] def Ex1.isOdd : Nat → Bool :=
|
|
fun a => isEven._mutual (PSum.inr a)
|
|
-/
|
|
#guard_msgs in
|
|
#print isOdd
|
|
|
|
#print isEven._mutual
|
|
|
|
end Ex1
|