Open tchajed opened 1 year ago
You mean cvc5 right?
If that's the case, then your PR should probably be rewritten as adding a new cvc5 driver if that's not too much trouble 🐱
I actually did mean CVC4. I can't find it in a changelog but the commit goes back to March 2018 and it was already in CVC4 1.6.
I've also been using CVC5 by just using the CVC4 driver with "cvc5" as the binary name; I haven't tested all that much but so far it has been compatible.
It looks like CVC4 does now support
check-sat-assuming
, as of https://github.com/cvc5/cvc5/pull/1637. This PR adds support for it and adds a test using activation literals.Here's a small test file that CVC4 correctly produces unsat for: