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.)
24 lines
634 B
Text
24 lines
634 B
Text
import Lean
|
||
|
||
open Lean
|
||
open Lean.Meta
|
||
|
||
def test (f : Expr) : MetaM Unit := do
|
||
let some thm ← mkCongrSimp? f | unreachable!
|
||
check thm.type
|
||
check thm.proof
|
||
assert! (← isDefEq thm.type (← inferType thm.proof))
|
||
IO.println (← Meta.ppExpr thm.type)
|
||
|
||
/--
|
||
info: ∀ (p p_1 : Prop), p = p_1 → ∀ {h : Decidable p} [h_1 : Decidable p_1], decide p = decide p_1
|
||
-/
|
||
#guard_msgs in
|
||
#eval test (mkConst ``decide)
|
||
|
||
/--
|
||
info: ∀ {α : Type} (a a_1 : Array α) (e_a : a = a_1) (i i_1 : USize) (e_i : i = i_1) (h : i.toNat < a.size),
|
||
a.uget i h = a_1.uget i_1 ⋯
|
||
-/
|
||
#guard_msgs in
|
||
#eval test (mkConst ``Array.uget [levelZero])
|