lean4-htt/tests/lean/run/grind_many_eqs.lean
Leonardo de Moura 3e2f1faebf
feat: add user-defined fallback procedure for the grind tactic (#6512)
This PR introduces support for user-defined fallback code in the `grind`
tactic. The fallback code can be utilized to inspect the state of
failing `grind` subgoals and/or invoke user-defined automation. Users
can now write `grind on_failure <code>`, where `<code>` should have the
type `GoalM Unit`. See the modified tests in this PR for examples.
2025-01-02 23:56:51 +00:00

30 lines
936 B
Text

import Lean.Meta.Tactic.Grind
def f (a : Nat) := a + a + a
def g (a : Nat) := a + a
def h (n : Nat) : Prop :=
match n with
| 0 => f 0 = f 1
| n+1 => f (n+1) = f n ∧ g (2*n + 1) = g (2*n) ∧ h n
-- Prints the equivalence class containing a `f` application
open Lean Meta Grind in
def fallback (n : Nat) : Fallback := do
let f0 ← Grind.shareCommon (mkApp (mkConst ``f) (mkNatLit 0))
-- The `f 0` equivalence class contains `n+1` elements
assert! (← getEqc f0).length == n + 1
forEachENode fun node => do
if node.self.isAppOf ``g then
-- Any equivalence class containing a `g`-application contains 2 elements
assert! (← getEqc (← getRoot node.self)).length == 2
(← get).mvarId.admit
set_option grind.debug true in
example : h 5 → False := by
simp [h]
grind on_failure fallback 5
set_option maxRecDepth 2048
example : h 100 → False := by
simp [h]
grind on_failure fallback 100