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
Boolector 3.0.0 (freshly built out of github sources) prints:
success
success
success
success
sat
success
((x #b00000000))
This is not standards compliant, since the printing of success in response to get-value should not be there. (That is, after the sat response, we shouldn't see a success, but directly the printing of the valuation pair.) If you try it with other solvers (z3, yices, cvc4), you can see that success isn't printed after we see sat.
This might sound like nit-picking, but unfortunately, it breaks compatibility with tools that operate on top of SMT-solvers; and is a real issue for me. Would be great if it can be fixed!
The text was updated successfully, but these errors were encountered:
For this input:
Boolector 3.0.0 (freshly built out of github sources) prints:
This is not standards compliant, since the printing of
success
in response toget-value
should not be there. (That is, after thesat
response, we shouldn't see asuccess
, but directly the printing of the valuation pair.) If you try it with other solvers (z3, yices, cvc4), you can see thatsuccess
isn't printed after we seesat
.This might sound like nit-picking, but unfortunately, it breaks compatibility with tools that operate on top of SMT-solvers; and is a real issue for me. Would be great if it can be fixed!
The text was updated successfully, but these errors were encountered: