potassco / potassco/constraint-handler
The recoverable operator mechanism is buggy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 0
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 20
Description
In the compile engine, when a operation with non-recoverable operator and some bad argument is evaluated, we may obtain two results: the value bad because the operator is not recoverable, and some other value coming from the operator definition itself. Ideally, a non-recoverable operator wouldn't have to ever have to examine bad arguments in its definition.
Unit tests bool_equivalence_bad and expression_bad_equality illustrate the issue.
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
Start in the compile engine and run the unit tests bool_equivalence_bad and expression_bad_equality, which illustrate the duplicate-result behavior. Trace evaluation of an operation with a non-recoverable operator and a bad argument. Done means the non-recoverable path no longer produces both the bad value and a value from the operator definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100