runtimeverification / runtimeverification/haskell-backend
Consider adding no-junk and no-confusion axioms to SMT prelude
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
The current SMT prelude for a definition does not use any no-junk nor no-confusion axioms.
We have an integration test that currently fails with booster-dev because of this lack.
Experiment with adding no-junk and no-confusion axioms to the SMT prelude
- Does the test pass with these axioms?
- Do the additional axioms cause significant overhead in large semantics?
Another, probably more principled, way to solve this could be to use SMT data types (which will imply their own no-junk and no-confusion axioms).
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 with the failing integration test and the SMT prelude referenced in commit c90f7a26da03b9257af4e7c4a83112c31004335d. Experiment with no-junk and no-confusion axioms, verify whether the test passes, and measure their overhead on large semantics; SMT data types are an alternative to compare.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100