runtimeverification / runtimeverification/kontrol
CSE: Apply range constraints to enums and mappings
Open
Nobody has claimed this yet.
cse
engagement
enhancement
- Dominant language
- Python
- Stars
- 122
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
To improve performance and facilitate CSE, we should allow
- Adding range constraints on enums to limit spurious branches;
- Applying range constraints of any form to mappings — the benefit would be the cutting of spurious branches and removal of chops, but the cost might be too much, since this would involve generating simplifications, which is something we don’t really do, but also making sure they are applicable at runtime, which might involve
smt-lemmas.
Contributor guide
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
No files, tests, or entry points are named. Start by tracing how CSE currently handles enums, mappings, and range constraints, then determine the required simplification and runtime-application behavior. Done means constraints reduce spurious branches and chops without producing invalid runtime assumptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100