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.)
23 lines
583 B
Text
23 lines
583 B
Text
--
|
||
|
||
/-- info: And.intro {a b : Prop} (left : a) (right : b) : a ∧ b -/
|
||
#guard_msgs in
|
||
#check And.intro
|
||
|
||
/--
|
||
info: @Or.rec : ∀ {a b : Prop} {motive : a ∨ b → Prop},
|
||
(∀ (h : a), motive ⋯) → (∀ (h : b), motive ⋯) → ∀ (t : a ∨ b), motive t
|
||
-/
|
||
#guard_msgs in
|
||
#check @Or.rec
|
||
|
||
/-- info: Eq.{u_1} {α : Sort u_1} : α → α → Prop -/
|
||
#guard_msgs in
|
||
#check Eq
|
||
|
||
/--
|
||
info: @Eq.rec : {α : Sort u_2} →
|
||
{a : α} → {motive : (a_1 : α) → a = a_1 → Sort u_1} → motive a ⋯ → {a_1 : α} → (t : a = a_1) → motive a_1 t
|
||
-/
|
||
#guard_msgs in
|
||
#check @Eq.rec
|