Skip to content
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.

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

Unexpectet behavior when not specifing a complete valuation #3

Open
Timo-Weike opened this issue Nov 11, 2019 · 1 comment
Open

Unexpectet behavior when not specifing a complete valuation #3

Timo-Weike opened this issue Nov 11, 2019 · 1 comment
Assignees
Labels
bug Something isn't working invalid This doesn't seem right question Further information is requested

Comments

@Timo-Weike
Copy link
Owner

If one calls logicly -e "a:0" "a or b" the program responds with False, but this seems not right since not all literals in the expression are bound through the valuation.


version 0.1.0.0-alpha

@Timo-Weike Timo-Weike added bug Something isn't working invalid This doesn't seem right question Further information is requested labels Nov 11, 2019
@Timo-Weike Timo-Weike self-assigned this Nov 11, 2019
@Timo-Weike
Copy link
Owner Author

Timo-Weike commented Nov 11, 2019

This behavior comes about through the assumption that every literal that is not set in the valuation is false (0). But I see that this unexpected or even undesirable behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working invalid This doesn't seem right question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant