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.)
33 lines
552 B
Text
33 lines
552 B
Text
import Lean
|
|
|
|
open Lean
|
|
open Lean.Meta
|
|
def tst (declName : Name) : MetaM Unit := do
|
|
IO.println (← getUnfoldEqnFor? declName)
|
|
|
|
def g (i j : Nat) : Nat :=
|
|
if i < 5 then 0 else
|
|
match j with
|
|
| Nat.zero => 1
|
|
| Nat.succ j => g i j
|
|
|
|
/-- info: (some g.eq_def) -/
|
|
#guard_msgs in
|
|
#eval tst ``g
|
|
#check g.eq_1
|
|
#check g.eq_2
|
|
#check g.eq_def
|
|
|
|
def h (i j : Nat) : Nat :=
|
|
let z :=
|
|
match j with
|
|
| Nat.zero => 1
|
|
| Nat.succ j => h i j
|
|
z + z
|
|
|
|
/-- info: (some h.eq_def) -/
|
|
#guard_msgs in
|
|
#eval tst ``h
|
|
#check h.eq_1
|
|
#check h.eq_2
|
|
#check h.eq_def
|