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.)
25 lines
529 B
Text
25 lines
529 B
Text
import Lean.Meta
|
|
|
|
|
|
open Lean
|
|
open Lean.Meta
|
|
|
|
axiom simple : forall {p q : Prop}, p → q → p
|
|
|
|
def print (msg : MessageData) : MetaM Unit := do
|
|
trace[Meta.Tactic] msg
|
|
|
|
def tst1 : MetaM Unit := do
|
|
let cinfo ← getConstInfo `simple
|
|
let mvar ← mkFreshExprSyntheticOpaqueMVar cinfo.type
|
|
let mvarId := mvar.mvarId!
|
|
let (_, mvarId) ← introN mvarId 4
|
|
assumption mvarId
|
|
let result ← instantiateMVars mvar
|
|
print result
|
|
|
|
set_option trace.Meta.Tactic true
|
|
|
|
/-- info: [Meta.Tactic] fun {p q} a a_1 => a -/
|
|
#guard_msgs in
|
|
#eval tst1
|