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.)
11 lines
267 B
Text
11 lines
267 B
Text
|
|
def f : Nat → Nat → Nat
|
|
| 0, b => b+1
|
|
| a+1, b => f a (f a b)
|
|
|
|
theorem ex1 (b) : f 0 b = b+1 := rfl
|
|
theorem ex2 (b) : f 1 b = (b+1)+1 := rfl
|
|
theorem ex3 (b) : f 2 b = b+1+1+1+1 := rfl
|
|
theorem ex4 (a b) : f (a+1) b = f a (f a b) := rfl
|
|
|
|
#guard f 2 5 == 9
|