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
369 B
Text
15 lines
369 B
Text
def foo: List Unit → Type
|
|
| [] => Unit → Unit
|
|
| _ :: tl => foo tl
|
|
|
|
partial def bar: (l: List Unit) → foo l → foo l
|
|
| [] , f => λ t => f t
|
|
| _ :: tl, f => bar tl f
|
|
|
|
def bar': (l: List Unit) → foo l → foo l
|
|
| [] , f => by simp only [foo] at f; exact (λ t => f t)
|
|
| _ :: tl, f => bar' tl f
|
|
|
|
/-- info: () -/
|
|
#guard_msgs in
|
|
#eval bar [()] id ()
|