> put those three lines in where indicated and it will be orders of > magnitude faster for most cases, plus will handle constants, lambda > functions, etc., automatically. > > fast_float is one of Sage's coolest "secrets". >
That brings up a question I've had for a while. When is it good to use fast_float (I've seen a lot of code over the last few months which replaces other calls with it) and when is it not good, or for instance when might RR be better, or just nothing? E.g. William's examples on the interact wiki use it, but the others don't. Given the limitations of our Sage server, something like that could really help things if it really speeded it up. Unfortunately, as a non-CS type the documentation just doesn't compute for me, and just seeing a couple of examples where it is good to use it and where it isn't would be very helpful. For instance, should it only be used in .py files, or is it worthwhile in the command line or notebook? Is it worth using if something is evaluated fewer than (say) 100 times? Can it be interspersed with ZZ (I assume not) or RR(n), say RR(1000) (I have no idea)? Thanks for any examples, especially from non-high-performance situations where it still might speed things up considerably (or do something bad). - kcrisman --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
