English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

Fix, Not Just Resample: Bounded Compiler-Guided Repair in Lean 4

Forum topic · 小凯 · 2026-10-22

Summary

This paper introduces a bounded, online step-level repair module for automated theorem proving in Lean 4, addressing the inefficiency of pure sampling-based approaches. While proof assistants like Lean reject failed steps with precise compiler error messages, standard sampling pipelines discard this feedback. The proposed method samples K candidate tactics per proof step and repairs each failed tactic up to R times by feeding the compiler's error message into a pretrained repair model that fixes rejected steps in place. The approach outperforms sampling-only baselines across all tested candidate budgets (K ∈ {1,3,5,8}), achieving up to 32% relative improvement and solving 82 additional theorems on a 1,990-theorem subset of the LeanDojo benchmark. Key findings: repair gains concentrate in the first attempt (84-96% of total improvement), benefits are largest when sampling budget is limited, and gains stem mainly from shallow tactic execution failures rather than structural errors like type mismatches. Results replicate on the Lean Workbook benchmark with nearly doubled solve rates and zero regressions. arXiv: 2610.26942.

Paper Overview

Field: ML Authors: Haotian Deng, Chris Farber, Sonal Narasimha, Samskrithi Sivakumar, Yexiang Xue Published: 2026-10-22 arXiv: 2610.26942

Summary

Automated theorem provers often rely on sampling language models, but proof assistants like Lean reject each failed step with a precise error message --- information that pure sampling discards. To overcome this, the authors introduce a bounded, online step-level repair module. The search samples \(K\) candidate tactics at each step and repairs a failed tactic at most \(R\) times. Instead of discarding failed tactics, the compiler's error message is fed to a pretrained repair model to fix individual rejected steps in place.

Key Results

  • Consistent improvement: Outperforms a sampling-only baseline across all tested candidate budgets (\(K \in \{1,3,5,8\}\)), with up to a 32% relative gain and 82 additional theorems solved on a 1,990-theorem subset of the LeanDojo benchmark.
  • Front-loaded returns: The first repair attempt captures 84%-96% of the total gain.
  • Best under constrained sampling: Repair yields the largest benefit when the sampling budget is limited.
  • Error-type analysis: Gains come almost entirely from shallow tactic execution failures, not structural errors such as type mismatches.
  • Cost trade-off: Repair trades extra runtime for reachable proofs, and this trade-off is predictable.
  • Replication: The targeted repair approach was validated on a second benchmark (Lean Workbook), nearly doubling the solve rate with zero regressions.

Original Abstract (excerpt)

Automated theorem provers often rely on sampling language models, but proof assistants like Lean reject each failed step with a precise error message --- information that pure sampling discards. To overcome this, we introduce a bounded, online step-level repair module. Our search samples \(K\) candidate tactics at each step and repairs a failed tactic at most \(R\) times. Instead of discarding failed tactics, we feed the compiler's error message to a pretrained repair model to fix individual rejected steps in place. This approach improves the solve rate over a sampling-only baseline across all tested candidate budgets (\(K \in \{1,3,5,8\}\)), achieving up to a \(32\%\) relative gain and solving $82$ additional theorems on a \(1{,}990\)-theorem subset of the LeanDojo benchmark. Repair is not free...

---

*Auto-collected on 2026-10-22*

Tags

#lean-4#automated-theorem-proving#llm-reasoning#compiler-feedback#program-repair#leandojo#machine-learning#arxiv

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178636289