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.)
48 lines
733 B
Text
48 lines
733 B
Text
import Lean
|
|
set_option autoImplicit false
|
|
|
|
namespace Foo.Bar
|
|
abbrev Bar := Nat
|
|
end Foo.Bar
|
|
|
|
open Foo Bar in
|
|
def myNat1 : Bar := 10 -- good
|
|
|
|
namespace Bar
|
|
end Bar
|
|
|
|
open Foo Bar in
|
|
def myNat2 : Bar := 10
|
|
|
|
open Foo.Bar in
|
|
def myNat3 : Bar := 10 -- good
|
|
|
|
open Foo Bar in
|
|
def myNat4 : Bar.Bar := 10 -- good
|
|
|
|
section
|
|
open Lean Parser Elab Tactic
|
|
|
|
/-- info: Lean.Parser.Tactic.rwRule : ParserDescr -/
|
|
#guard_msgs in
|
|
#check rwRule
|
|
|
|
/-- info: Lean.Elab.Tactic.evalDSimp : Tactic -/
|
|
#guard_msgs in
|
|
#check evalDSimp
|
|
end
|
|
|
|
section
|
|
open Lean
|
|
|
|
/-- info: Lean.Parser.Tactic.rwRule : ParserDescr -/
|
|
#guard_msgs in
|
|
#check Parser.Tactic.rwRule
|
|
|
|
open Parser
|
|
|
|
/-- info: Lean.Parser.Tactic.rwRule : ParserDescr -/
|
|
#guard_msgs in
|
|
#check Tactic.rwRule
|
|
|
|
end
|