You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Relevancy propagation is on.
The literal where query!0_0_n appears is irrelevant.
So the model contains no assignment for query!0_0_n.
You could give this literal any truth value you like.
Then everything works correctly in release mode, while the assertion is still useful in development mode to see if anything better can be done for similar cases that come from real applications.
Do you want me to close this, or hide the assertion?
It is a very peculiar case: It is processing the equality
(= (* 2 query!0_0_n) query!0_1_n)
Model evaluation determines that it is false, because query!0_1_n = 1 (even parity cannot be = 1),
but does not bind a value to query!0_0_n. Then later on it doesn't evaluate
(< (* 2 query!0_0_n) query!0_1_n)
to a definite value.
OS: Ubuntu 18.04
Commit: 799b613
The text was updated successfully, but these errors were encountered: