leanprover-community / leanprover-community/mathlib4
Tracking issue: targets for faster tactics
Open
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 4.2k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
This issue exists to track locations where a tactic can (or does) close a goal but does so slowly.
The idea is that by highlighting such locations, we obtain data which can inform efforts to optimise existing tactics or inspire new ones.
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
Use this issue as a tracking list for locations where tactics close goals slowly; no file, test, or entry point is specified. A contribution would need a concrete location and agreed optimization target before implementation can be scoped.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100