#3955: make find_minimum_on_interval use _fast_float_
-------------------------------------+--------------------------------------
Reporter: was | Owner: burcin
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-5.6
Component: calculus | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: Timo Kluck
Authors: Andrzej Giniewicz | Merged in:
Dependencies: #2607 | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by tkluck):
jdemeyer: sorry about the milestone change, I didn't realize 5.5 was
already in the RC stage.
ppurka: if I understand it correctly, all the other
`find_{min,max}imum_on_interval` functions have already been changed to
use `fast_float`. So already from a consistency point of view, this one
should be, too.
Of course, you still have a point. Especially since before, you could
always manually pass a `fast_float` function if you needed the speedup,
but now you cannot disable that feature if you need the precision.
Maybe there should be something like a safe version of fast float, that
checks its results for `NaN` or `Inf` and if so, redoes the calculation
with the original expression.
I think that this patch should still be applied for consistency. Maybe
such a safe version of `fast_float` could be the solution to #13559?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/3955#comment:16>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
