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.)
37 lines
653 B
Text
37 lines
653 B
Text
|
|
def foo (x : Nat) : IO Bool := do
|
|
if x == 0 then
|
|
throw $ IO.userError "foo: unexpected zero"
|
|
pure (x == 1)
|
|
|
|
def tst (x : Nat) : IO Unit := do
|
|
if x == 0 then
|
|
IO.println "x is 0"
|
|
else if (← foo x) then
|
|
IO.println "x is 1"
|
|
else
|
|
IO.println "other"
|
|
|
|
/-- info: x is 0 -/
|
|
#guard_msgs in
|
|
#eval tst 0
|
|
|
|
/-- info: x is 1 -/
|
|
#guard_msgs in
|
|
#eval tst 1
|
|
|
|
/-- info: other -/
|
|
#guard_msgs in
|
|
#eval tst 2
|
|
|
|
syntax term "<|||>" term : doElem
|
|
|
|
macro_rules
|
|
| `(doElem| $a:term <|||> $b) => `(doElem| if (← $a) then pure true else $b:term)
|
|
|
|
def tst2 : IO Bool := do
|
|
pure true <|||> (← throw $ IO.userError "failed")
|
|
|
|
/-- info: true -/
|
|
#guard_msgs in
|
|
#eval tst2
|