runtimeverification / runtimeverification/mir-semantics
Refactor module structure for runtime modules
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 52
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Maybe we can just move code to different modules when we modify or extend it.
There was already a proposal to refactor the modules,. adding an umbrella runtime.md file and module.
Having an overall RUNTIME module is certainly a good thing, too. In which case the code from kmir.md that handles statements and terminators should move to its own module as well, and kmir.md only imports other things and defines the very top (#init, which we don't even use).
Originally posted by @jberthold in https://github.com/runtimeverification/mir-semantics/pull/674#discussion_r2329519238
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 reviewing the proposal in PR 674 and the current module layout, especially kmir.md. Compare the proposed runtime.md umbrella module with the existing statement and terminator definitions. Done means the runtime structure is agreed and the relevant definitions are organized under the intended modules without changing semantics.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100