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.)
22 lines
470 B
Text
22 lines
470 B
Text
import Lean
|
||
|
||
open Lean
|
||
open Lean.Meta
|
||
def tst (declName : Name) : MetaM Unit := do
|
||
IO.println (← getUnfoldEqnFor? declName)
|
||
|
||
inductive Wk: Nat -> Nat -> Type 0 where
|
||
| id: Wk n n
|
||
| step: Wk m n -> Wk (Nat.succ m) n
|
||
|
||
def wk_comp : Wk n m → Wk m l → Wk n l
|
||
| Wk.id, σ => σ
|
||
| Wk.step ρ, σ => Wk.step (wk_comp ρ σ)
|
||
|
||
/-- info: (some wk_comp.eq_def) -/
|
||
#guard_msgs in
|
||
#eval tst ``wk_comp
|
||
|
||
#check @wk_comp.eq_1
|
||
#check @wk_comp.eq_2
|
||
#check @wk_comp.eq_def
|