-
Notifications
You must be signed in to change notification settings - Fork 5
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
avoid calling SMT solver for "true" and "false" #139
Labels
Comments
Smattr
added a commit
that referenced
this issue
Jun 26, 2019
These literals are already as simple as they can be. Any attempt to ask the SMT solver to simplify them just produces themselves. So avoid calling the solver altogether in these cases. Github: closes #139 "avoid calling SMT solver for "true" and "false""
Smattr
added a commit
that referenced
this issue
Jun 27, 2019
These literals are already as simple as they can be. Any attempt to ask the SMT solver to simplify them just produces themselves. So avoid calling the solver altogether in these cases. Github: closes #139 "avoid calling SMT solver for "true" and "false""
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In relation to #130, the implementation in the feature/smt-solver branch is pretty unintelligent and calls the SMT solver for any boolean expression. This includes the literals
true
andfalse
, which is a waste of time as the algorithm is only capable of replacing these with themselves. We should just detect this and avoid calling the solver in this case.The text was updated successfully, but these errors were encountered: