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.)
24 lines
486 B
Text
24 lines
486 B
Text
example (a : Nat) : let n := 0; n + a = a := by
|
|
intro n
|
|
fail_if_success simp (config := { zeta := false })
|
|
simp (config := { zeta := false }) [n]
|
|
|
|
/--
|
|
info: a b : Nat
|
|
h : a = b
|
|
n : Nat := 0
|
|
⊢ n + a = b
|
|
---
|
|
info: a b : Nat
|
|
h : a = b
|
|
n : Nat := 0
|
|
⊢ a = b
|
|
-/
|
|
#guard_msgs in
|
|
example (a b : Nat) (h : a = b) : let n := 0; n + a = b := by
|
|
intro n
|
|
fail_if_success simp (config := { zeta := false })
|
|
trace_state
|
|
simp (config := { zeta := false }) [n]
|
|
trace_state
|
|
simp [h]
|