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.)
39 lines
834 B
Text
39 lines
834 B
Text
import Lean
|
|
|
|
open Lean
|
|
|
|
partial def mkBig : Nat → Expr
|
|
| 0 => mkConst `a
|
|
| (n+1) => mkApp2 (mkConst `f []) (mkBig n) (mkBig n)
|
|
|
|
def replaceTest (e : Expr) : Expr :=
|
|
e.replace $ fun e => match e with
|
|
| Expr.const c _ => if c == `f then mkConst `g else none
|
|
| _ => none
|
|
|
|
#eval replaceTest $ mkBig 4
|
|
|
|
/-- info: Lean.Expr.const `g [] -/
|
|
#guard_msgs in
|
|
#eval (replaceTest $ mkBig 128).getAppFn
|
|
|
|
def findTest (e : Expr) : Option Expr :=
|
|
e.find? $ fun e => match e with
|
|
| Expr.const c _ => c == `g
|
|
| _ => false
|
|
|
|
/-- info: none -/
|
|
#guard_msgs in
|
|
#eval findTest $ mkBig 4
|
|
|
|
/-- info: some (Lean.Expr.const `g []) -/
|
|
#guard_msgs in
|
|
#eval findTest $ replaceTest $ mkBig 4
|
|
|
|
/-- info: none -/
|
|
#guard_msgs in
|
|
#eval findTest $ mkBig 128
|
|
|
|
/-- info: some (Lean.Expr.const `g []) -/
|
|
#guard_msgs in
|
|
#eval findTest $ (replaceTest $ mkBig 128)
|