rocq-prover / rocq-prover/stdlib
Setoid rewriting hardcodes stdlib paths instead of relying on Register
Open
Nobody has claimed this yet.
- Dominant language
- Rocq Prover
- Stars
- 42
- Forks
- 38
- Avg merge
- 14h 6m
- Merged PRs (30d)
- 3
Description
https://coq.zulipchat.com/#narrow/stream/237977-Coq-users/topic/Setoid.20rewrite.20with.20no.20init asks how to reuse setoid rewriting with HoTT; tactics/rewrite.ml hardcodes what's needed in the stdlib. Could it use Register instead?
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 with tactics/rewrite.ml and the linked Zulip discussion about using setoid rewriting with HoTT and no init. Identify the stdlib paths currently hardcoded there and trace how Register could provide them instead. Done means setoid rewriting no longer depends on those hardcoded paths and the requested HoTT use case is addressed.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100