You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I definitely don't think we should always use BigInt.
In any case the whole conversion and atomic stuff really needs to be rewritten.
Currently there seem to be many conversions that are far too slow because they are going through atomic and trying to be too clever.
We should reduce all the cleverness and use it only when using @interval and the string macros.
In trying to make an
Interval{BigFloat}
out of 0.1 ± √eps(0.1), the resulting interval width is actually eps(0.1):The same happens if we change the strategy:
Digging on the code, I've found that
..
callsatomic
, which callsrationalize
, which should have aBigInt
first argument forBigFloat
numbers:So that the following workaround produces the desired
Interval
:The text was updated successfully, but these errors were encountered: