runtimeverification / runtimeverification/mir-semantics

Simplify K code for writing `Moved` values

Open
#627 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
52
Forks
5
No merged PRs in 30d

Description

As a follow-up to TypedValue -> Value PR #625 , writing Moved could be simpler, within #setLocalValue

  • currently #setLocalValue is never called with Moved values
  • would fail to write if the local is immutable
  • could be fixed with a dedicated rule for Moved or an orBool in the requires clause (which anyway has to change to avoid duplicate rule application)
  • #writeMoved and #forceSetLocal would be obsolete

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at #setLocalValue and trace how Moved values are handled, then inspect #writeMoved and #forceSetLocal in the codebase. Review PR #625 for context. Done means Moved values write correctly, including for immutable locals, without duplicate rule application, and the obsolete helpers are removed.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.