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.)
22 lines
406 B
Text
22 lines
406 B
Text
set_option pp.analyze false
|
|
|
|
/--
|
|
warning: declaration uses 'sorry'
|
|
---
|
|
info: p : (n : Nat) → Fin n → Prop
|
|
n : Nat
|
|
v : Fin n
|
|
n' : Nat
|
|
v' : Fin n'
|
|
h₁ : n.succ = n'
|
|
h₂ : HEq v.succ v'
|
|
⊢ p n' v'
|
|
-/
|
|
#guard_msgs in
|
|
example (p : (n : Nat) → Fin n → Prop)
|
|
(n : Nat)
|
|
(v : Fin n)
|
|
: p n.succ v.succ := by
|
|
generalize h₁ : n.succ = n', h₂ : v.succ = v'
|
|
trace_state
|
|
admit
|