lean4-htt/tests/lean/run/doLetElse.lean
Kim Morrison 3a457e6ad6
chore: use #guard_msgs in run tests (#4175)
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.)
2024-05-16 00:38:31 +00:00

40 lines
786 B
Text

def foo (x? : Option Nat) : IO Nat := do
let some x := x? | return 0
IO.println s!"x: {x}"
return x
def testFoo (input : Option Nat) (expected : Nat) : IO Unit := do
assert! (← foo input) == expected
/-- info: x: 10 -/
#guard_msgs in
#eval testFoo (some 10) 10
/-- info: -/
#guard_msgs in
#eval testFoo none 0
/-- info: x: 1 -/
#guard_msgs in
#eval testFoo (some 1) 1
def bar (x : Nat) : IO (Fin (x + 1)) := do
let 2 := x | return 0
-- the pattern match performed a substitution
let y : Fin 3 := ⟨1, by decide⟩
return y
def testBar (x : Nat) (expected : Fin (x + 1)) : IO Unit := do
assert! (← bar x) == expected
/-- info: -/
#guard_msgs in
#eval testBar 1 0
/-- info: -/
#guard_msgs in
#eval testBar 2 1
/-- info: -/
#guard_msgs in
#eval testBar 3 0