leanprover-community / leanprover-community/iris-lean
feat: allow tracking of `rocq_concept`s which are blocked by other concept's implementation
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 218
- Forks
- 63
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 22
Description
I think it would also be useful to link to some other Rocq definitions in a #rocq_ignore command, to say that the ignored definition hasn't been implemented because it depends on some other definitions which have not yet been implemented (and implementing them was out of scope at the time). Maybe something to be added as part of the status in the rocq_concept command.
Envisioned syntax
#rocq_concept "program_logic/language.v" stuckness_to_atomicity (waiting_on stuckness)
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 locating the implementations of the #rocq_concept and #rocq_ignore commands, then trace how ignored definitions and their status are recorded. Use the proposed waiting_on syntax as the behavioral target; done means a rocq_concept can record blocked Rocq definitions and expose that dependency without breaking existing commands.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100