daniel-raffler

I've now opened a second pull request with just the floating point changes [here](https://github.com/sosy-lab/java-smt/pull/354).

I've updated this branch to use the new TermManager interface from Bitwuzla (see [here](https://github.com/bitwuzla/bitwuzla/commits/refactor-node-manager/)).

Updated to the latest git version. Bitwuzla now has a new method to read back variables/functions that were defined during a parser run (see [here](https://github.com/bitwuzla/bitwuzla/discussions/101#discussioncomment-8753080)). This helps us fix some...

I've had a closer look at this bug since I've run into the same issue while working on the new SolverThreadLocalityTest class for bug #347. The problem is that CVC5...

I've now opened a discussion on the CVC5 bugtracker: https://github.com/cvc5/cvc5/discussions/10265

CVC5 now has a new "TermManger" interface that should solve our problem: https://github.com/cvc5/cvc5/pull/10426 https://github.com/cvc5/cvc5/pull/10531 I'll start working on an update to the solver backend in the next few days. EDIT:...

I've opened a discussion about our remaining issue with floating point values in Bitwuzla: https://github.com/bitwuzla/bitwuzla/discussions/103

I've just added a build script for packaging the dReal solver backend. It is still quite basic and will only repackage the binaries that are povided by the dReal team....

This is a bug in CVC5 and I reported it [here](https://github.com/cvc5/cvc5/issues/10256)

I've opened a new discussion about our issues with the parser on the Bitwuzla bugtracker: https://github.com/bitwuzla/bitwuzla/discussions/101