leanprover-community / leanprover-community/mathlib4
Priority mechanism for `hint` tactic
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 4.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
It might be nice if the hint tactic had a priority mechanism, with tactics that generally run quickly having high priority and tactics that run slowly having low priority. This way, we could ensure the tactic is roughly as responsive as possible, while not needing to carefully order the register_hints.
Alternatively, we could run each tactic repeatedly with a heartbeat limit until it succeeded or failed, exponentially backing off on the limit size.
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
No files, tests, or entry points are identified in the issue. Start by locating the hint tactic and its register_hint mechanism, then determine the intended priority or heartbeat behavior and define completion around a responsive, working tactic implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100