lean4-htt/tests/lean/run/983.lean
Kim Morrison 3a457e6ad6
chore: use #guard_msgs in run tests (#4175)
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.)
2024-05-16 00:38:31 +00:00

29 lines
696 B
Text

import Lean
-- The `cases` tactic does not use `Lean.Meta.cases` under the hood,
-- so it is unaffected by this issue. We define a tactic
-- `mcases` that delegates to `Lean.Meta.cases`.
syntax (name := mcases) "mcases" ident : tactic
namespace Lean.Elab.Tactic
@[tactic mcases]
def evalMcases : Tactic
| `(tactic| mcases $hyp) => do
let hyp ← getFVarId hyp
liftMetaTactic fun goal => do
let goals ← goal.cases hyp
return goals.map (·.mvarId) |>.toList
| _ => unreachable!
end Lean.Elab.Tactic
example : True := by
let h : ∃ n, n = 0 := ⟨0, rfl⟩
mcases h
sorry -- sorry
example : True := by
have h : ∃ n, n = 0 := ⟨0, rfl⟩
mcases h
apply True.intro