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
618 B
Text
24 lines
618 B
Text
instance : DecidableEq ByteArray
|
|
| ⟨a⟩, ⟨b⟩ => match decEq a b with
|
|
| isTrue h₁ => isTrue $ congrArg ByteArray.mk h₁
|
|
| isFalse h₂ => isFalse $ fun h => by cases h; cases (h₂ rfl)
|
|
|
|
/-- info: true -/
|
|
#guard_msgs in
|
|
#eval ByteArray.empty = ByteArray.empty
|
|
|
|
/-- info: true -/
|
|
#guard_msgs in
|
|
#eval ByteArray.empty != ByteArray.empty.push 5
|
|
|
|
instance : BEq FloatArray where
|
|
beq a b := match a, b with
|
|
| ⟨a⟩, ⟨b⟩ => a == b
|
|
|
|
/-- info: true -/
|
|
#guard_msgs in
|
|
#eval FloatArray.empty == FloatArray.empty
|
|
|
|
/-- info: true -/
|
|
#guard_msgs in
|
|
#eval FloatArray.empty != FloatArray.empty.push 5
|