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
487 B
Text
17 lines
487 B
Text
def small (ps : Array (Nat × Nat)) : Array (Nat × Nat) :=
|
||
(ps.filter fun (p : Prod _ _) =>
|
||
match p with
|
||
| (x, y) => x == 0)
|
||
++
|
||
ps
|
||
|
||
#guard small #[(1, 2), (0, 3), (2, 4)] == #[(0, 3), (1, 2), (0, 3), (2, 4)]
|
||
|
||
variable {α β : Type} [Inhabited α] [Inhabited β]
|
||
|
||
def P (xys : Array (α × β)) (f : α → β) : Prop := True
|
||
|
||
example (xys : Array (α × β))
|
||
(pred? : α → Bool)
|
||
(H : Subtype $ P (xys.filter fun (x, _) => pred? x))
|
||
: Unit := ()
|