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.)
26 lines
507 B
Text
26 lines
507 B
Text
def p (x : Prop) := x
|
|
|
|
@[simp] theorem lemma1 (x : Prop) : p x = x :=
|
|
rfl
|
|
|
|
theorem ex1 (x : Prop) (h : x) : p x := by
|
|
simp
|
|
assumption
|
|
|
|
/--
|
|
info: theorem ex1 : ∀ (x : Prop), x → p x :=
|
|
fun x h => id h
|
|
-/
|
|
#guard_msgs in
|
|
#print ex1
|
|
|
|
theorem ex2 (x : Prop) (q : Prop → Prop) (h₁ : x) (h₂ : q x = x) : q x := by
|
|
simp [h₂]
|
|
assumption
|
|
|
|
/--
|
|
info: theorem ex2 : ∀ (x : Prop) (q : Prop → Prop), x → q x = x → q x :=
|
|
fun x q h₁ h₂ => Eq.mpr (id h₂) h₁
|
|
-/
|
|
#guard_msgs in
|
|
#print ex2
|