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.)
33 lines
539 B
Text
33 lines
539 B
Text
@[simp] def foo (a : Nat) : Nat :=
|
|
2 * a
|
|
|
|
/--
|
|
info: case h
|
|
x : Nat
|
|
⊢ 2 * x = x + x
|
|
-/
|
|
#guard_msgs in
|
|
example : foo = fun a => a + a :=
|
|
by
|
|
fail_if_success simp -- should not unfold `foo` into a lambda
|
|
funext x
|
|
simp -- unfolds `foo`
|
|
trace_state
|
|
simp_arith
|
|
|
|
@[simp] def boo : Nat → Nat
|
|
| a => 2 * a
|
|
|
|
/--
|
|
info: case h
|
|
x : Nat
|
|
⊢ 2 * x = x + x
|
|
-/
|
|
#guard_msgs in
|
|
example : boo = fun a => a + a :=
|
|
by
|
|
fail_if_success simp -- should not unfold `boo` into a lambda
|
|
funext x
|
|
simp -- unfolds `boo`
|
|
trace_state
|
|
simp_arith
|