runtimeverification / runtimeverification/stable-mir-json
Consts are not necessarily `Scalar` values
Open
Nobody has claimed this yet.
Future Work Notes
- Dominant language
- Rust
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Consts that are evaluated (not UnevaluatedConst) may not be Scalar and instead be complex types that are evaluated to byte strings. This is a problem with the current memory layout as abstract.
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 how evaluated Const and UnevaluatedConst are represented in the Rust library, then inspect the current abstract memory layout for its Scalar assumption. Determine how complex evaluated constants that become byte strings should be represented; done means the layout no longer requires every evaluated constant to be Scalar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100