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.)
34 lines
462 B
Text
34 lines
462 B
Text
|
||
|
||
universe u v
|
||
|
||
inductive arrow (α : Type u) (β : Type v)
|
||
| mk : (α → β) → arrow α β
|
||
|
||
inductive foo
|
||
| mk : arrow Nat foo → foo
|
||
|
||
/--
|
||
info: inductive foo : Type
|
||
number of parameters: 0
|
||
constructors:
|
||
foo.mk : arrow Nat foo → foo
|
||
-/
|
||
#guard_msgs in
|
||
#print foo
|
||
|
||
#print foo.rec
|
||
set_option pp.all true
|
||
#print foo.below
|
||
|
||
mutual
|
||
|
||
inductive foo2 : Type
|
||
| mk : arrow2 → foo2
|
||
|
||
inductive arrow2 : Type
|
||
| mk : (Nat → foo2) → arrow2
|
||
|
||
end
|
||
|
||
#print foo2.brecOn
|