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.)
24 lines
376 B
Text
24 lines
376 B
Text
import Lean
|
|
|
|
open Lean
|
|
|
|
def x := 10
|
|
|
|
unsafe def tst : CoreM Unit := do
|
|
let env ← getEnv
|
|
IO.println $ env.evalConst Nat {} `x
|
|
|
|
/-- info: ok: 10 -/
|
|
#guard_msgs in
|
|
#eval tst
|
|
|
|
def f (x : Nat) := x + 1
|
|
|
|
unsafe def tst2 : CoreM Unit := do
|
|
let env ← getEnv
|
|
let f ← IO.ofExcept $ env.evalConst (Nat → Nat) {} `f
|
|
IO.println $ (f 10)
|
|
|
|
/-- info: 11 -/
|
|
#guard_msgs in
|
|
#eval tst2
|