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.)
41 lines
762 B
Text
41 lines
762 B
Text
abbrev M := ExceptT String $ ExceptT Nat $ StateM Nat
|
|
|
|
def inc (x : Nat) : M Unit := do
|
|
if (← get) >= 100 then
|
|
throwThe Nat ((← get) + x)
|
|
modify (· + x)
|
|
|
|
def dec (x : Nat) : M Unit := do
|
|
if (← get) - x == 0 then
|
|
throw "balance is zero"
|
|
modify (· - x)
|
|
|
|
def f (x y : Nat) : M Nat := do
|
|
try
|
|
inc x
|
|
dec y
|
|
get
|
|
catch ex : String =>
|
|
dbg_trace "string exception {ex}"
|
|
pure 1000
|
|
catch ex : Nat =>
|
|
dbg_trace "nat exception {ex}"
|
|
pure ex
|
|
|
|
/--
|
|
info: nat exception 1010
|
|
(Except.ok (Except.ok 1010), 1000)
|
|
-/
|
|
#guard_msgs in
|
|
#eval (f 10 20).run 1000
|
|
|
|
/--
|
|
info: string exception balance is zero
|
|
(Except.ok (Except.ok 1000), 20)
|
|
-/
|
|
#guard_msgs in
|
|
#eval (f 10 200).run 10
|
|
|
|
/-- info: (Except.ok (Except.ok 20), 20) -/
|
|
#guard_msgs in
|
|
#eval (f 10 20).run 30
|