-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
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
Float binding issues #291
Comments
I think the first point is possible with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The high-level library provides limited
Float
support, but what is present seems to be below the minimum necessary to make use of float sorts.Float
Ast
.Float
s cannot be displayed as their human-readable value, instead displaying hex forms of the raw sign, exponent, and mantissa bits. While these values can technically be extracted and reparsed to bypass the first limitation, this is unlikely to be the library's intended solution.Float
s to and fromReal
values or expose necessaryRoundingMode
functionality to implement suchReal
conversions in a useful manner.Float
behaviour as a library consumer is heavily limited by No way to access the rawZ3_sort
fromSort<'ctx>
orZ3_context
fromContext
#290, which also limits attempts at improvements which could eventually be integrated into the library if they prove useful.Z3_mk_fpa_mul
is bound incorrectly, as may be othertrinop
s; It is supposed to receivemul(ctx, roundingMode, fpAst, fpAst)
, but is instead receivingmul(ctx, fpAst, fpAst, fpAst)
, which causes floats to always hit theis_null
assertion during themul
invocation; This appears to be untested.The text was updated successfully, but these errors were encountered: