runtimeverification / runtimeverification/haskell-backend
`checkImplicationWorker` presents misleading state when a proof is stuck
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:
This state is returned and printed to the user, but it is not the proof state which is stuck. It is an artefact from the checking algorithm. In case of NotImplied, the check routine returns the original claimPattern, whereas here (NotImpliedStuck) it returns part of its negation.
This will confuse users.
Related: #3218 , possibly #3116
Scope
Investigate whether more useful output can be presented to the user in stuck states.
If this is not possible, print additional information for the user to understand the output.
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 lines 159-167 and inspect checkImplicationWorker in the related reachability code. Determine whether stuck states can present the actual proof state; if not, add information that explains the displayed output, then update the unit test to show the more useful result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100