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.)
77 lines
734 B
Text
77 lines
734 B
Text
|
|
|
|
def ex1 : IO Unit := do
|
|
IO.println "example 1"
|
|
for x in [:100:10] do
|
|
IO.println s!"x: {x}"
|
|
|
|
/--
|
|
info: example 1
|
|
x: 0
|
|
x: 10
|
|
x: 20
|
|
x: 30
|
|
x: 40
|
|
x: 50
|
|
x: 60
|
|
x: 70
|
|
x: 80
|
|
x: 90
|
|
-/
|
|
#guard_msgs in
|
|
#eval ex1
|
|
|
|
def ex2 : IO Unit := do
|
|
IO.println "example 2"
|
|
for x in [:10] do
|
|
IO.println s!"x: {x}"
|
|
|
|
/--
|
|
info: example 2
|
|
x: 0
|
|
x: 1
|
|
x: 2
|
|
x: 3
|
|
x: 4
|
|
x: 5
|
|
x: 6
|
|
x: 7
|
|
x: 8
|
|
x: 9
|
|
-/
|
|
#guard_msgs in
|
|
#eval ex2
|
|
|
|
def ex3 : IO Unit := do
|
|
IO.println "example 3"
|
|
for x in [1:10] do
|
|
IO.println s!"x: {x}"
|
|
|
|
/--
|
|
info: example 3
|
|
x: 1
|
|
x: 2
|
|
x: 3
|
|
x: 4
|
|
x: 5
|
|
x: 6
|
|
x: 7
|
|
x: 8
|
|
x: 9
|
|
-/
|
|
#guard_msgs in
|
|
#eval ex3
|
|
|
|
def ex4 : IO Unit := do
|
|
IO.println "example 4"
|
|
for x in [1:10:3] do
|
|
IO.println s!"x: {x}"
|
|
|
|
/--
|
|
info: example 4
|
|
x: 1
|
|
x: 4
|
|
x: 7
|
|
-/
|
|
#guard_msgs in
|
|
#eval ex4
|