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.)
27 lines
637 B
Text
27 lines
637 B
Text
set_option linter.unusedVariables false
|
|
|
|
opaque f (x y : Nat) : Nat
|
|
opaque g (x : Nat) : Nat
|
|
|
|
theorem ex1 (x : Nat) (h₁ : f x x = g x) (h₂ : g x = x) : f x (f x x) = x := by
|
|
fail_if_success simp
|
|
simp [*]
|
|
|
|
theorem ex2 (x : Nat) (h₁ : f x x = g x) (h₂ : g x = x) : f x (f x x) = x := by
|
|
simp [*]
|
|
|
|
axiom g_ax (x : Nat) : g x = 0
|
|
|
|
/--
|
|
info: x y : Nat
|
|
h₁ : f x x = g x
|
|
h₂ : g x < 5
|
|
⊢ g x + g x = 0
|
|
-/
|
|
#guard_msgs in
|
|
theorem ex3 (x y : Nat) (h₁ : f x x = g x) (h₂ : f x x < 5) : f x x + f x x = 0 := by
|
|
simp [*] at *
|
|
trace_state
|
|
have aux₁ : f x x = g x := h₁
|
|
have aux₂ : g x < 5 := h₂
|
|
simp [g_ax]
|