runtimeverification / runtimeverification/haskell-backend
`checkImplicationWorker` unable to prove a correct implication
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
When inspecting a unit test:
The backend should be able to determine that this condition is \bottom (\exists Y. x == y is true for element variables x).
The test is actually wrong, as f(x) => \exists y. f(y) is true even if f is undefined. This implication should result in Implied, not NotImpliedStuck.
Possible reason: The side condition (LHS of the implication) is not used when simplifying, therefore the SMT solver does not get enough information to solve the predicate.
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 kore/test/Test/Kore/Reachability/Claim.hs at lines 159-167 and trace checkImplicationWorker for this implication. Inspect whether the left-hand side is available during simplification and SMT solving; done when the test expects Implied instead of NotImpliedStuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100