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.)
30 lines
626 B
Text
30 lines
626 B
Text
--
|
||
|
||
axiom p {α β} : α → β → Prop
|
||
axiom foo {α β} (a : α) (b : β) : p a b
|
||
|
||
example : p 0 0 := by simp [foo]
|
||
example (a : Nat) : p a a := by simp [foo a]
|
||
example : p 0 0 := by simp [foo 0]
|
||
example : p 0 0 := by simp [foo 0 0]
|
||
example : p 0 0 := by
|
||
fail_if_success
|
||
simp [foo 1] -- will not simplify
|
||
simp [foo 0]
|
||
|
||
/-- info: ⊢ p 0 0 -/
|
||
#guard_msgs in
|
||
example : p 0 0 ∧ p 1 1 := by
|
||
simp [foo 1]
|
||
trace_state
|
||
simp [foo 0]
|
||
|
||
namespace Foo
|
||
|
||
axiom p {α} : α → Prop
|
||
axiom foo {α} [ToString α] (n : Nat) (a : α) : p a
|
||
|
||
example : p 0 := by simp [foo 0]
|
||
example : p 0 ∧ True := by simp [foo 0]
|
||
|
||
end Foo
|