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.)
17 lines
305 B
Text
17 lines
305 B
Text
|
|
|
|
def main : IO Unit := do
|
|
IO.println ((2 : Float).sin);
|
|
IO.println ((2 : Float).cos);
|
|
IO.println ((2 : Float).sqrt);
|
|
IO.println ((2 : Float) ^ (200 : Float));
|
|
pure ()
|
|
|
|
/--
|
|
info: 0.909297
|
|
-0.416147
|
|
1.414214
|
|
1606938044258990275541962092341162602522202993782792835301376.000000
|
|
-/
|
|
#guard_msgs in
|
|
#eval main
|