leanprover / leanprover/lean4

Some builtin tactics do not have their config types in `Init`

Open
#9,306 2 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

The syntax of builtin elaborators such as solve_by_elim and apply_rules (did not find any other) are defined in Init, but their config types are not.
This leads to an elaboration failure for the config type in e.g., solve_by_elim -backtracking.

Context
Steps to Reproduce
example : True := by
  solve_by_elim -backtracking

Expected behavior: No elaboration failure; should prove the goal

Actual behavior: error evaluating configuration, environment does not yet contain type Lean.Meta.SolveByElim.SolveByElimConfig

Versions

"4.23.0-nightly-2025-07-10"

Additional Information
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

Begin with the builtin elaborator definitions in Init for solve_by_elim and apply_rules, then inspect how their configuration types are resolved. Run the provided solve_by_elim -backtracking example as the initial reproduction. Done means the example elaborates without the missing SolveByElimConfig error and proves the goal.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.