lean4-htt/tests/lean/run/dsimp1.lean
Kim Morrison 3a457e6ad6
chore: use #guard_msgs in run tests (#4175)
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.)
2024-05-16 00:38:31 +00:00

29 lines
591 B
Text

def Nat.isZero (x : Nat) : Bool :=
match x with
| 0 => true
| x+1 => false
/--
info: x : Nat
⊢ (1 + x).isZero = false
-/
#guard_msgs in
example (x : Nat) : (1 + id x.succ.pred).isZero = false := by
dsimp
trace_state
simp [Nat.succ_add]
dsimp [Nat.isZero]
#check Nat.pred_succ
example (x : Nat) : (id x.succ.succ).isZero = false := by
dsimp [Nat.isZero]
example (x : Nat) : (id x.succ.succ).isZero = false := by
dsimp!
@[simp] theorem isZero_succ (x : Nat) : (x + 1).isZero = false :=
rfl
theorem ex1 (x : Nat) : (id x.succ.succ.pred).isZero = false := by
dsimp