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.)
43 lines
1,020 B
Text
43 lines
1,020 B
Text
def mkByteArray (n : Nat) : ByteArray := Id.run <| do
|
|
let mut r := {}
|
|
for i in [:n] do
|
|
r := r.push (UInt8.ofNat i)
|
|
return r
|
|
|
|
def tst1 (n : Nat) (expected : UInt32) : IO Unit := do
|
|
let bs := mkByteArray n
|
|
let sum := bs.foldl (init := 0) fun s b => s + b.toUInt32
|
|
assert! sum == expected
|
|
IO.println sum
|
|
|
|
/-- info: 4950 -/
|
|
#guard_msgs in
|
|
#eval tst1 100 4950
|
|
|
|
def tst2 (n : Nat) (expected : UInt32) : IO Unit := do
|
|
let bs := mkByteArray n
|
|
let mut sum := 0
|
|
for b in bs do
|
|
sum := sum + b.toUInt32
|
|
assert! sum == expected
|
|
IO.println sum
|
|
|
|
/-- info: 4950 -/
|
|
#guard_msgs in
|
|
#eval tst2 100 4950
|
|
|
|
def tst3 (n : Nat) (expected : UInt32) : IO Unit := do
|
|
let bs := mkByteArray n
|
|
let mut sum := 0
|
|
for i in [:bs.size] do
|
|
sum := sum + bs[i]!.toUInt32
|
|
assert! sum == expected
|
|
IO.println sum
|
|
|
|
/-- info: 4950 -/
|
|
#guard_msgs in
|
|
#eval tst3 100 4950
|
|
|
|
set_option trace.compiler.ir.result true in
|
|
def computeByteHash (bytes : ByteArray) :=
|
|
bytes.foldl (init := 1723) fun h b => mixHash h (hash b)
|