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.)
26 lines
562 B
Text
26 lines
562 B
Text
import Lean
|
|
|
|
|
|
open Lean
|
|
|
|
def c1 : Bool := true
|
|
|
|
unsafe def tst1 : CoreM Unit := do
|
|
let env ← getEnv;
|
|
let v := env.evalConst Bool {} `c1;
|
|
IO.println v
|
|
|
|
/-- info: ok: true -/
|
|
#guard_msgs in
|
|
#eval tst1 -- used to output incorrect value (ok false). Reason: the unboxed value `true` is `1`, but the boxed `false` value is also `1`.
|
|
|
|
def c2 : Bool := false
|
|
|
|
unsafe def tst2 : CoreM Unit := do
|
|
let env ← getEnv;
|
|
let v := env.evalConst Bool {} `c2;
|
|
IO.println v
|
|
|
|
/-- info: ok: false -/
|
|
#guard_msgs in
|
|
#eval tst2 -- used to crash since `0` is not a valid boxed value
|