leanprover / leanprover/lean4

Pattern-matching on `repeat` tactic fails with infinite loop

Open
#10,154 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug P-medium
Dominant language
Lean
Stars
9.2k
Forks
990
Avg merge
1d 17h
Merged PRs (30d)
175

Description

Prerequisites

Please put an X between the brackets as you perform the following steps:

Description

MWE:

import Lean

run_cmd do
  let t ← `(tactic| repeat fail) -- works
  match t with
  | `(tactic| repeat fail) => return -- max recursion depth has been reached
  | _ => return

I suspect this issue affects any recursive macro. E.g. this fails in the same way:

syntax "silly" : tactic
macro_rules
  | `(tactic| silly) => `(tactic| first | skip | silly)

run_cmd do
  let t ← `(tactic| silly) -- works
  match t with
  | `(tactic| silly) => return -- max recursion depth has been reached
  | _ => return
Versions
Lean 4.24.0-nightly-2025-08-26
Target: x86_64-unknown-linux-gnu
Impact

Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the minimal repeat fail and silly examples from the issue against the specified Lean nightly. Trace the tactic quotation pattern matching that reaches the recursion-depth error; done means both matches terminate without the infinite loop or recursion-depth failure.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.