leanprover-community / leanprover-community/iris-lean
doc: Codify a consistent set of rules for `#rocq_ignore` and `rocq_alias`
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Lean
- Stars
- 218
- Forks
- 63
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 22
Description
When the port is done we should sweep the repo and decide which rocq_ignores can be upgraded to rocq_alias. At the moment, we are not consistent with this. It is not urgent, but would be nice to have the rules codified somehow.
- Should
Propers be ignored, or implemented and aliased? - Rocq syntax classes (
Dist,Valid, etc) that are not present in Lean. For instances of these classes so we ignore these, or say their alias is the field of their class implementation? Should we implement the syntax classes?
Contributor guide
No contributing guide indexed for this repository
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 surveying the repository for existing #rocq_ignore and rocq_alias uses after the port is complete. Review how Propers and Rocq syntax classes such as Dist and Valid are currently handled, then document consistent rules and apply them across the repository.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100