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.)
20 lines
424 B
Text
20 lines
424 B
Text
class Approx {α : Type} (a : α) (X : Type) : Type where
|
||
val : X
|
||
|
||
variable {α β X Y : Type} {f' : α → β} {x' : α} [f : Approx f' (X → Y)] [x : Approx x' X]
|
||
|
||
-- fails
|
||
/-- info: Approx.val f' (Approx.val x') : Y -/
|
||
#guard_msgs in
|
||
#check f.val x.val
|
||
|
||
-- works
|
||
/--
|
||
info: let f'' := Approx.val f';
|
||
let x'' := Approx.val x';
|
||
f'' x'' : Y
|
||
-/
|
||
#guard_msgs in
|
||
#check let f'' := f.val
|
||
let x'' := x.val
|
||
f'' x''
|