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.)
24 lines
445 B
Text
24 lines
445 B
Text
|
|
|
|
def tst : IO Unit :=
|
|
do
|
|
let bs := [(1 : Float), 2, 3].toFloatArray;
|
|
IO.println bs;
|
|
let bs := bs.push (4 : Float);
|
|
let bs := bs.set! 1 (20 / 3);
|
|
IO.println bs;
|
|
let bs₁ := bs.set! 2 30;
|
|
IO.println bs₁;
|
|
IO.println bs;
|
|
IO.println bs.size;
|
|
pure ()
|
|
|
|
/--
|
|
info: [1.000000, 2.000000, 3.000000]
|
|
[1.000000, 6.666667, 3.000000, 4.000000]
|
|
[1.000000, 6.666667, 30.000000, 4.000000]
|
|
[1.000000, 6.666667, 3.000000, 4.000000]
|
|
4
|
|
-/
|
|
#guard_msgs in
|
|
#eval tst
|