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.)
22 lines
499 B
Text
22 lines
499 B
Text
@[simp] def g (x y : Nat) : Nat :=
|
|
match x, y with
|
|
| 0, 0 => 1
|
|
| 0, y => y
|
|
| x+1, 5 => 2 * g x 0
|
|
| x+1, y => 2 * g x y
|
|
|
|
/-- info: g.eq_1 : g 0 0 = 1 -/
|
|
#guard_msgs in
|
|
#check g.eq_1
|
|
|
|
/-- info: g.eq_2 (y : Nat) (x_2 : y = 0 → False) : g 0 y = y -/
|
|
#guard_msgs in
|
|
#check g.eq_2
|
|
|
|
/-- info: g.eq_3 (x_2 : Nat) : g x_2.succ 5 = 2 * g x_2 0 -/
|
|
#guard_msgs in
|
|
#check g.eq_3
|
|
|
|
/-- info: g.eq_4 (y x_2 : Nat) (x_3 : y = 5 → False) : g x_2.succ y = 2 * g x_2 y -/
|
|
#guard_msgs in
|
|
#check g.eq_4
|