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.)
36 lines
717 B
Text
36 lines
717 B
Text
inductive Foo : Nat -> Type where
|
|
| mk (a b : Nat) : Foo a -> Foo b
|
|
|
|
/-- info: Foo.mk : (a b : Nat) → Foo a → Foo b -/
|
|
#guard_msgs in
|
|
#check @Foo.mk
|
|
example : (a b : Nat) → Foo a → Foo b := @Foo.mk
|
|
|
|
/--
|
|
info: inductive Foo : Nat → Type
|
|
number of parameters: 0
|
|
constructors:
|
|
Foo.mk : (a b : Nat) → Foo a → Foo b
|
|
-/
|
|
#guard_msgs in
|
|
#print Foo
|
|
|
|
namespace Ex2
|
|
|
|
def natToType : Nat → Type
|
|
| 0 => Unit
|
|
| _ => Bool
|
|
|
|
inductive Foo : Nat → Char → Prop
|
|
| mk (n : Nat) (elem : natToType n) (c : Char) : Foo n c
|
|
|
|
/--
|
|
info: inductive Ex2.Foo : Nat → Char → Prop
|
|
number of parameters: 1
|
|
constructors:
|
|
Ex2.Foo.mk : ∀ (n : Nat), natToType n → ∀ (c : Char), Foo n c
|
|
-/
|
|
#guard_msgs in
|
|
#print Foo
|
|
|
|
end Ex2
|