runtimeverification / runtimeverification/stable-mir-json
Incorporate feedback on our stable-MIR and its extraction
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
- multi-body functions should not exist (once monomorphic)
- extraction code first determines all instances and then converts to stable, should invert that
- unevaluated constants should not exist in monomorphic code
- binders should not exist
- possibly more... (complete this as we go)
Generally, first calling the conversion to stable MIR should remove these cases.
If internal MIR is required, we should note the case and report it.
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 tracing the stable-MIR conversion and extraction paths named in the issue. Check how multi-body functions, unevaluated constants, and binders are handled after conversion, and identify any internal MIR cases that must be reported. Done means these cases are removed from monomorphic stable MIR or explicitly reported, with the remaining cases clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100