grind sets
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 709
- Forks
- 200
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 45
Description
https://github.com/leanprover/lean4/pull/11765 adds user-defined grind attributes, analogous to custom simp sets. I think this could have several advantages over the current practice of using scoped grind. Tying grind rules to namespaces can be problematic when they are deeply nested, causing us to make annotations with attribute away from their definitions or keep track of overly specific scopes. With grind sets, we could define high level sets of rules (LTS, Automata, etc.) without being concerned about these naming details.
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
Start by reading PR 11765 and the existing uses of scoped grind attributes, then compare them with the linked simp-set documentation. Done means defining the intended user-defined grind-set behavior and resolving how high-level sets such as LTS or Automata should avoid namespace-specific annotations.
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
- Mostly clear
- Newbie friendliness
- 28/100