lean4-htt/tests/lean/run/strInterpolation.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

42 lines
568 B
Text

#eval s!"hello {1+1}"
def tst (x : Nat) : IO Unit := do
IO.println s!"x: {x}"
IO.println s!"x+1: {x+1}"
/--
info: x: 10
x+1: 11
-/
#guard_msgs in
#eval tst 10
/-- info: "1+1" -/
#guard_msgs in
#eval s!"{1}+{1}"
/-- info: "{2}" -/
#guard_msgs in
#eval s!"\{{1+1}}"
/-- info: "a1" -/
#guard_msgs in
#eval s!"a{1}"
def g (x : Nat) : StateRefT Nat IO Nat := do
modify (· + x)
get
def ex : StateRefT Nat IO Unit := do
IO.println s!">> hello {(←g 1)}"
IO.println s!">> world {(←g 1)}"
pure ()
/--
info: >> hello 1
>> world 2
-/
#guard_msgs in
#eval ex.run' 0