Some builtin tactics do not have their config types in `Init`
Nobody has claimed this yet.
- 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:
- Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues - Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries. - Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- 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