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.)
15 lines
615 B
Text
15 lines
615 B
Text
def as := [-1, 2, 0, -3, 4]
|
|
|
|
#guard as.map (fun a => ite (GE.ge a 0) [a] []) == [[], [2], [0], [], [4]]
|
|
|
|
-- Used to fail if we use `withSynthesize` instead of `withSynthesizeLight` at `elabBinRel`
|
|
#guard as.map (fun a => ite (a ≥ 0) [a] []) = [[], [2], [0], [], [4]]
|
|
|
|
example : True :=
|
|
/-
|
|
Requires type annotation at the numeral, otherwise we get a type error at `rfl`
|
|
because `(0 == 1)` does not reduce to `false` until the default instance is applied.
|
|
Possible improvement: before reporting a type mismatch, apply default instances, and try again.
|
|
-/
|
|
have : (0 == (1 : Nat)) = false := rfl
|
|
⟨⟩
|