-
Notifications
You must be signed in to change notification settings - Fork 6
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
default show for Arb might be confusing #84
Comments
What is exactly the bug? My hunch is that in the second and third case the midpoint is not exactly what is printed. Printed is the rounded version. The first I guess is a concise printing. In the other cases the midpoint has an exact representation and is therefore abbreviated. |
the bug is that
the interval |
oh I see |
I don't think this is a bug but a result of the fact that
|
thanks for the explanation @Joel-Dahne; I found it confusing, but it makes perfect sense after explanation; however: given that this requires an explanation should we switch to |
That is a good point actually! I have actually been bitten a couple of times by this behaviour myself. The main risk I see with this is that reading that string back with |
I see, but given the problems with julia> x = Arblib.set_interval!(Arb(), Arf(1.0), Arf(2.0))
[+/- 2.01]
julia> y = Arb(Arblib.string_nice(x))
[+/- 2.02]
julia> Arblib.midref(y)
0
julia> z = Arb(Arblib.string_decimal(x)) # ← but not guaranteed to enclose x...
[+/- 2.01]
julia> Arblib.midref(z)
1.5
the functions for loading and storing are EDIT: |
This is an interval containing
0
:This is an interval containing
1
:This is an interval containing
1.5
:let's try the same with
set_interval!
:moreover:
The text was updated successfully, but these errors were encountered: