Skip to content

improve/fix handling of classical negation #268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Feb 22, 2021
Merged

improve/fix handling of classical negation #268

merged 2 commits into from
Feb 22, 2021

Conversation

rkaminsk
Copy link
Member

@rkaminsk rkaminsk commented Feb 20, 2021 •
edited
Loading

  • Fix handling of classical negation in incremental programs extended via grounding or the backend.
  • Add unit tests.

@rkaminsk rkaminsk self-assigned this Feb 20, 2021
@rkaminsk rkaminsk added the bug label Feb 20, 2021
@rkaminsk rkaminsk added this to the v5.5.0 milestone Feb 20, 2021
@rkaminsk rkaminsk linked an issue Feb 20, 2021 that may be closed by this pull request
Adding classically negated atoms via the backend leads to undesired results. #265
Closed
@rkaminsk rkaminsk force-pushed the bugfix/classical-negation branch from 160083a to 53cedb0 Compare February 22, 2021 10:44
@rkaminsk rkaminsk marked this pull request as ready for review February 22, 2021 10:52
@rkaminsk rkaminsk merged commit 360ee57 into wip Feb 22, 2021
@rkaminsk rkaminsk deleted the bugfix/classical-negation branch February 22, 2021 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@rkaminsk rkaminsk

Labels
bug
Projects
None yet
Milestone
v5.5.0
Development

Successfully merging this pull request may close these issues.

Adding classically negated atoms via the backend leads to undesired results.
1 participant
@rkaminsk