lean4-htt/tests/lean/run/elab_cmd.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

67 lines
1,001 B
Text

import Lean
open Lean.Elab.Term
open Lean.Elab.Command
elab "∃'" b:term "," P:term : term => do
let ex ← `(Exists (fun $b => $P));
elabTerm ex none
elab "#check2" b:term : command => do
let cmd ← `(#check $b #check $b);
elabCommand cmd
#check ∃' x, x > 0
#check ∃' (x : UInt32), x > 0
#check2 10
elab "try" t:tactic : tactic => do
let t' ← `(tactic| first | $t:tactic | skip);
Lean.Elab.Tactic.evalTactic t'
set_option linter.unusedVariables false
/--
info: case h₁
x y z : Nat
h1 : y = z
h2 : x = x
h3 : x = y
⊢ x = ?b
case h₂
x y z : Nat
h1 : y = z
h2 : x = x
h3 : x = y
⊢ ?b = z
case b
x y z : Nat
h1 : y = z
h2 : x = x
h3 : x = y
⊢ Nat
---
info: case h₂
x y z : Nat
h1 : y = z
h2 : x = x
h3 : x = y
⊢ y = z
-/
#guard_msgs in
theorem tst (x y z : Nat) : y = z → x = x → x = y → x = z :=
by {
intro h1; intro h2; intro h3;
apply @Eq.trans;
try exact h1; -- `exact h1` fails
trace_state;
try exact h3;
trace_state;
try exact h1;
}