-
Notifications
You must be signed in to change notification settings - Fork 33
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
CrackNum decimal printing #685
Comments
Another confusing output:
Note that the "note" says the conversion was exact, but we see |
Looking at the code, what we do is simply call Instead, we should call This is something we should do, but need a bit more digging to figure out exactly how to approach. For instance, it would be nice to add |
Triggering from sbv directly:
|
Consider:
This is correct; but extremely confusing! Why, because the decimal value as printed is an "equal" value that maps to this representation. But at first look, one would like to see 0.09375.
Note that 0.0938 isn't incorrect; because it maps to that very same value representationally. And it's probably picked by the underlying FPLib library because it's "shorter."
But this is clearly confusing. I wonder if we can represent the info in a better way to avoid such pitfalls.
The text was updated successfully, but these errors were encountered: