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.)
37 lines
868 B
Text
37 lines
868 B
Text
import Lean.Meta
|
|
|
|
open Lean
|
|
open Lean.Meta
|
|
|
|
def tst1 : MetaM Unit :=
|
|
withLocalDeclD `y (mkConst `Nat) $ fun y => do
|
|
withLetDecl `x (mkConst `Nat) (mkNatLit 0) $ fun x => do {
|
|
let mvar ← mkFreshExprMVar (mkConst `Nat) MetavarKind.syntheticOpaque;
|
|
trace[Meta.debug] mvar;
|
|
let r ← mkLambdaFVars #[y, x] mvar;
|
|
trace[Message.debug] r;
|
|
let v := mkApp2 (mkConst `Nat.add) x y;
|
|
assignExprMVar mvar.mvarId! v;
|
|
trace[Meta.debug] mvar;
|
|
trace[Meta.debug] r;
|
|
let mctx ← getMCtx;
|
|
mctx.decls.forM fun mvarId mvarDecl => do
|
|
trace[Meta.debug] m!"?{mvarId.name} : {mvarDecl.type}"
|
|
}
|
|
|
|
set_option trace.Meta.debug true
|
|
|
|
/--
|
|
info: [Meta.debug] ?m.3
|
|
[Meta.debug] x.add y
|
|
[Meta.debug] fun y =>
|
|
let x := 0;
|
|
x.add y
|
|
[Meta.debug] ?_uniq.4 : Nat →
|
|
Nat →
|
|
let x := 0;
|
|
Nat
|
|
[Meta.debug] ?_uniq.3 : Nat
|
|
-/
|
|
#guard_msgs in
|
|
#eval tst1
|