Robert Bradshaw wrote:
>
> I'd also like to point out that we don't just want to fall back and do
> everything over the rationals (even though any finite decimal
> expansion is rational) as things get much slower due to coefficient
> explosion. For example
Who cares about speed when the answer is wrong?
If I don't have to produce the correct answer, I can solve any problem
instantly. The current implementation over the reals might as well be,
def echelon_form(self):
return matrix([ [1,0,0], [0,1,0], [0,0,1] ])
and it doesn't get much faster than that.
> Note also that 0.3 and 3/10 have different behaviors in Sage,
> sometimes you want one, sometimes you want the other.
Retarded.
> Note that 0.3 can't even be represented exactly as a (binary) floating
> point number.
And that's why.
Correctness should be the default. If using n(3/10) is going to be a
couple of milliseconds faster, let the guy who cares about that type a
few 'n's. I shouldn't have to solve my problem by hand before feeding it
to SAGE just to get the correct answer.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
