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
393 B
Text
17 lines
393 B
Text
import Lean.Data.PersistentArray
|
||
|
||
def check [BEq α] (as : List α) : Bool :=
|
||
as.toPArray'.foldr (.::.) [] == as
|
||
|
||
def tst1 : IO Unit := do
|
||
assert! check [1, 2, 3]
|
||
assert! check ([] : List Nat)
|
||
assert! check (List.iota 17)
|
||
assert! check (List.iota 533)
|
||
assert! check (List.iota 1000)
|
||
assert! check (List.iota 2600)
|
||
IO.println "done"
|
||
|
||
/-- info: done -/
|
||
#guard_msgs in
|
||
#eval tst1
|