runtimeverification / runtimeverification/stable-mir-json
Graph Improvements: Mutability specifiers on locals
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Currently there are no mutability specifiers on locals, often this means trying to figure out from context, or the json artifact, or the KMIR proof state what the mutability is. Sometimes this information is not close together and it takes time to track down.
^^^ Local 3 must have been mutable, since Local 5 has a mutable reference to it.
Much like rust, probably the best representation is omitting information if it is immutable, and adding mut prefixed if it is mutable.
So the example in the image above, it would be clearer if it printed in the LOCALS:
3 = mut std::array::IntoIter<i32, 1>
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 code that renders the LOCALS entries in the graph or JSON artifact, then inspect how mutability is represented in the KMIR proof state. Update the displayed local type so mutable locals use the mut prefix while immutable locals omit it, and verify the example output matches the requested form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100