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.)
16 lines
431 B
Text
16 lines
431 B
Text
macro "foo" x:ident : command =>
|
|
`(structure Foo where
|
|
val : Nat
|
|
prop : val = 42
|
|
def f (x : Foo) := x.val
|
|
def g : Foo := { val := 42, prop := by decide }
|
|
theorem $x:ident (x : Foo) : f x = 42 := by simp [f, x.prop] )
|
|
|
|
foo test
|
|
|
|
/--
|
|
info: theorem test : ∀ (x : Foo✝), f✝ x = 42 :=
|
|
fun x => of_eq_true (Eq.trans (congrArg (fun x => x = 42) (Foo.prop✝ x)) (eq_self 42))
|
|
-/
|
|
#guard_msgs in
|
|
#print test
|