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.)
47 lines
698 B
Text
47 lines
698 B
Text
def f (x : Nat) : IO Nat := do
|
|
IO.println "hello"
|
|
if x > 5 then
|
|
IO.println ("x: " ++ toString x)
|
|
IO.println "done"
|
|
pure (x + 1)
|
|
|
|
/--
|
|
info: hello
|
|
3
|
|
-/
|
|
#guard_msgs in
|
|
#eval f 2
|
|
|
|
/--
|
|
info: hello
|
|
x: 10
|
|
done
|
|
11
|
|
-/
|
|
#guard_msgs in
|
|
#eval f 10
|
|
|
|
def g (x : Nat) : StateT Nat Id Unit := do
|
|
if x > 10 then
|
|
let s ← get
|
|
set (s + x)
|
|
pure ()
|
|
|
|
theorem ex1 : (g 10).run 1 = ((), 1) :=
|
|
rfl
|
|
|
|
theorem ex2 : (g 20).run 1 = ((), 21) :=
|
|
rfl
|
|
|
|
def h (x : Nat) : StateT Nat Id Unit := do
|
|
if x > 10 then {
|
|
let s ← get;
|
|
set (s + x) -- we don't need to respect indentation when `{` `}` are used
|
|
}
|
|
pure ()
|
|
|
|
theorem ex3 : (h 10).run 1 = ((), 1) :=
|
|
rfl
|
|
|
|
theorem ex4 : (h 20).run 1 = ((), 21) :=
|
|
rfl
|