-
Notifications
You must be signed in to change notification settings - Fork 72
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
Make fast powers (pow) the default #14
Comments
What do you think about this @lbenet? |
I think the default should be to get the tightest intervals, and it that sense, it shouldn't be the default. I wouldn't mind to have it as default for the Do you think that the current |
In this particular case, I don't agree. The reason is simply that using the tight For a real use case I just tried, just changing the two instances of As soon as I also don't think that we should change the behaviour based on the rounding type (more than is necessary). |
Just to make my point clear: I am in favor of the slow version ( My comment about the You are probably right; using |
My proposal is not to remove the tight version, just to not make it the default. |
I understand your point for the "gotcha" about the speed, and agree that the problem lies in the conversion to BigFloat's, performing there the calculations, and convert back to Float64. Yet, I think the aim of the package is reliability rather than speed, and this includes the tightness of the bounds. Tightness is so important that it is mentioned in the standard. We give the option to the user who prefers speed (by sacrificing tightness) which is the |
I recall that when I was dealing with |
I believe that the standard only requires documenting how strict each function is. The current pow is correct, and only slightly wider in most cases. |
I do think that the standard requires tightness for In any case, see #47 for an implementation of |
addressed in #388 |
Solved in PR #593. |
Make
^
use the fast version andpow
the slow but precise version usingBigFloat
(i.e., invert what currently happens).The text was updated successfully, but these errors were encountered: