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.)
20 lines
447 B
Text
20 lines
447 B
Text
import Lean
|
||
|
||
open Lean Meta Elab Tactic Grind in
|
||
elab "grind_pre" : tactic => do
|
||
liftMetaTactic fun mvarId => do
|
||
let result ← Meta.Grind.Preprocessor.main mvarId
|
||
return result.goals.map (·.mvarId) |>.toList
|
||
|
||
/--
|
||
warning: declaration uses 'sorry'
|
||
---
|
||
info: a b c : Bool
|
||
h : a = true ∧ (b = true ∨ c = true)
|
||
⊢ (b && a) = true
|
||
-/
|
||
#guard_msgs in
|
||
example (h : (a && (b || c)) = true) : b && a := by
|
||
grind_pre
|
||
trace_state
|
||
sorry
|