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.)
40 lines
609 B
Text
40 lines
609 B
Text
import Lean
|
|
set_option trace.Meta.debug true
|
|
class W where
|
|
/-- w -/
|
|
w : Unit
|
|
|
|
class X extends W where
|
|
/-- x -/
|
|
x : Unit
|
|
|
|
class Y extends W where
|
|
/-- y -/
|
|
y : Unit
|
|
|
|
class Y' extends Y where
|
|
/-- h -/
|
|
h : Uint
|
|
|
|
class Z extends X, Y'
|
|
|
|
open Lean
|
|
def test (declName : Name) : CoreM Unit := do
|
|
let some docstr ← findDocString? (← getEnv) declName | throwError "docstring not found"
|
|
IO.println docstr
|
|
|
|
/-- info: w -/
|
|
#guard_msgs in
|
|
#eval test ``W.w
|
|
|
|
/-- info: x -/
|
|
#guard_msgs in
|
|
#eval test ``X.x
|
|
|
|
/-- info: y -/
|
|
#guard_msgs in
|
|
#eval test ``Z.y
|
|
|
|
/-- info: h -/
|
|
#guard_msgs in
|
|
#eval test ``Z.h
|