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
Z3 supports (minimize ...) and (maximize ...) commands, as illustrated in this example. As far as I am aware, Z3 is the only solver that supports something like this at the moment, as other solvers would have to approximate this functionality with something like resolveBoundsSymBV (see #187). In fact, resolveBoundsSymBV is exactly why I'm opening this issue, as the test cases that I added for it run noticeably slower on Z3 than on, say, Yices or CVC4 (at least a couple of seconds slower). I'm wondering if using minimize/maximize could make things faster on Z3.
Z3 supports
(minimize ...)
and(maximize ...)
commands, as illustrated in this example. As far as I am aware, Z3 is the only solver that supports something like this at the moment, as other solvers would have to approximate this functionality with something likeresolveBoundsSymBV
(see #187). In fact,resolveBoundsSymBV
is exactly why I'm opening this issue, as the test cases that I added for it run noticeably slower on Z3 than on, say, Yices or CVC4 (at least a couple of seconds slower). I'm wondering if usingminimize
/maximize
could make things faster on Z3.I'm imagining the API would look something like:
This would need to be guarded behind a problem feature of some sort. SBV already supports something like this here.
The text was updated successfully, but these errors were encountered: