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
521 B
Text
23 lines
521 B
Text
structure FooS where
|
|
x : Nat
|
|
y : Nat
|
|
h : x = y := by rfl
|
|
|
|
/-- info: constructor FooS.mk : (x y : Nat) → autoParam (x = y) _auto✝ → FooS -/
|
|
#guard_msgs in
|
|
#print FooS.mk
|
|
|
|
def f1 (x : Nat) : FooS :=
|
|
{ x := x, y := x }
|
|
|
|
structure BooS where
|
|
x : Nat
|
|
y : Nat
|
|
h (aux1 : True) (aux2 : x > 2) : x = y := by { intros; rfl }
|
|
|
|
/-- info: constructor BooS.mk : (x y : Nat) → autoParam (True → x > 2 → x = y) _auto✝ → BooS -/
|
|
#guard_msgs in
|
|
#print BooS.mk
|
|
|
|
def f2 (x : Nat) : BooS :=
|
|
{ x := x, y := x }
|