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
What4 has code for automatically declaring tuple datatypes in solvers that speak SMTLib2 as necessary to interpret the BaseStruct type. Currently, this code apparently assumes the Z3 syntax for declaring datatypes, which does not match the SMTLib 2.6 syntax (CF http://smtlib.cs.uiowa.edu/papers/smt-lib-reference-v2.6-r2017-07-18.pdf).
As a result, the necessary tuple declarations fail on SMTLib 2.6 compliant solvers (e.g. CVC4). We should refactor the tuple declaration code to work correctly on as many solvers as possible.
The text was updated successfully, but these errors were encountered:
Fixes#54. Fixes#324. Note, however that #325 still applies. However, a bugfix is already applied in HEAD Z3 and the similar CVC4 error has been worked around by changing tuple representations.
What4 has code for automatically declaring tuple datatypes in solvers that speak SMTLib2 as necessary to interpret the
BaseStruct
type. Currently, this code apparently assumes the Z3 syntax for declaring datatypes, which does not match the SMTLib 2.6 syntax (CF http://smtlib.cs.uiowa.edu/papers/smt-lib-reference-v2.6-r2017-07-18.pdf).As a result, the necessary tuple declarations fail on SMTLib 2.6 compliant solvers (e.g. CVC4). We should refactor the tuple declaration code to work correctly on as many solvers as possible.
The text was updated successfully, but these errors were encountered: