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.)
17 lines
435 B
Text
17 lines
435 B
Text
class Class.{u} where
|
|
dummy : PUnit.{u}
|
|
|
|
def notWork [Class.{u}] : PUnit := Class.dummy
|
|
def alsoNotWork [Class.{1}] : PUnit := Class.dummy
|
|
def work [Class.{u}] : PUnit.{u} := Class.dummy
|
|
def alsoWork [Class.{u}] := Class.dummy.{u}
|
|
|
|
|
|
class Category.{v, u} (Ob : Type u) where
|
|
Hom : Ob → Ob → Type v
|
|
|
|
variable (C : Type u) [Category.{v} C] (X : C)
|
|
|
|
/-- info: Category.Hom X X : Type v -/
|
|
#guard_msgs in
|
|
#check (Category.Hom X X)
|