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.)
43 lines
1,004 B
Text
43 lines
1,004 B
Text
inductive Foo1 (F : {n : Nat} → Type) : Type where
|
|
| bar : Foo1 _
|
|
|
|
/-- info: @Foo1.bar : {F : {n : Nat} → Type} → Foo1 F -/
|
|
#guard_msgs in
|
|
#check @Foo1.bar
|
|
|
|
inductive Foo2 (F : {n : Nat} → Type) : Type where
|
|
| bar : Foo2 F
|
|
|
|
/-- info: @Foo2.bar : {F : {n : Nat} → Type} → Foo2 F -/
|
|
#guard_msgs in
|
|
#check @Foo2.bar
|
|
|
|
inductive Foo3 (F : {n : Nat} → Type) : Type where
|
|
| bar : Foo3 @F
|
|
|
|
/-- info: @Foo3.bar : {F : {n : Nat} → Type} → Foo3 F -/
|
|
#guard_msgs in
|
|
#check @Foo3.bar
|
|
|
|
inductive Bla1 (F : {n : Nat} → Type) : Type where
|
|
| mk : Bla1 _
|
|
| bar : Bla1 _ → Bla1 _
|
|
|
|
/-- info: @Bla1.bar : {F : {n : Nat} → Type} → Bla1 F → Bla1 F -/
|
|
#guard_msgs in
|
|
#check @Bla1.bar
|
|
|
|
mutual
|
|
|
|
inductive Boo1 (F : {n : Nat} → Type) : Type where
|
|
| mk : Boo1 _
|
|
| bar : Zoo1 _ → Boo1 F → Boo1 _
|
|
|
|
inductive Zoo1 (F : {n : Nat} → Type) : Type where
|
|
| bar : Boo1 _ → Zoo1 _
|
|
|
|
end
|
|
|
|
/-- info: @Boo1.bar : {F : {n : Nat} → Type} → Zoo1 F → Boo1 F → Boo1 F -/
|
|
#guard_msgs in
|
|
#check @Boo1.bar
|