runtimeverification / runtimeverification/mir-semantics
Implement execution rules for `Statement`
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Here is an issue to track the Stable MIR Statements we currently have implemented in mir-semantics:
- Assign(Place, Rvalue)
- FakeRead(FakeReadCause, Place)
- S1etDiscriminant { place: Place, variant_index: VariantIdx }
- Deinit(Place)
- StorageLive(Local)
- StorageDead(Local)
- Retag(RetagKind, Place)
- PlaceMention(Place)
- AscribeUserType { place: Place, projections: UserTypeProjection, variance: Variance }
- Coverage(Coverage)
- Intrinsic(NonDivergingIntrinsic)
- ConstEvalCounter
- Nop
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 with the linked Stable MIR Statements definitions and locate the mir-semantics implementation of Assign, which is already marked complete. Trace how the remaining unchecked statement variants are represented and executed, and consider the work done when each listed rule is implemented and verified consistently with the existing Assign rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100