We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
well, it's an edge case, but here goes:
[send->] (get-value (v15)) [<-recv] ((v15 0.0)) -- fine, has decimal point [send->] (get-value (0.0)) [<-recv] ((0.0 0)) -- not fine
this sometimes happens in my application (some expressions might have been simplified but I do not keep track of it)
cvc5 sends back 0.0.
cvc5
0.0
It's a bit hard to fix in simple-smt, since getExprs is not typed. I can fix it in my application https://gitlab.imn.htwk-leipzig.de/waldmann/pure-matchbox/-/commit/a9dd4017030d7992132de745708ebfb2cabd51fb because I have typed expressions there.
getExprs
The text was updated successfully, but these errors were encountered:
test case for yav#20
1926f53
Agreed that this sort of thing should probably be handled in the application using simple-stm. Do we need to do something for this ticket?
simple-stm
Sorry, something went wrong.
No branches or pull requests
well, it's an edge case, but here goes:
this sometimes happens in my application (some expressions might have been simplified but I do not keep track of it)
cvc5
sends back0.0
.It's a bit hard to fix in simple-smt, since
getExprs
is not typed. I can fix it in my application https://gitlab.imn.htwk-leipzig.de/waldmann/pure-matchbox/-/commit/a9dd4017030d7992132de745708ebfb2cabd51fb because I have typed expressions there.The text was updated successfully, but these errors were encountered: