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.)
15 lines
431 B
Text
15 lines
431 B
Text
import Lean
|
|
open Lean
|
|
open Lean.Meta
|
|
|
|
def test : MetaM Unit := do
|
|
let x ← mkFreshExprMVar (mkConst ``Nat)
|
|
let y ← mkFreshExprMVar (mkConst ``Nat)
|
|
let add := mkConst ``Nat.add
|
|
let e := mkApp3 add x (mkNatLit 1) y
|
|
IO.println (e.abstract #[x, y])
|
|
assert! e.abstract #[x, y] == mkApp3 add (mkBVar 1) (mkNatLit 1) (mkBVar 0)
|
|
|
|
/-- info: Nat.add #1 (OfNat.ofNat.{0} Nat 1 (instOfNatNat 1)) #0 -/
|
|
#guard_msgs in
|
|
#eval test
|