Hi William, On 2015-07-13, William Stein <[email protected]> wrote: > Despite what other people are saying in this thread, I definitely 100% > consider the above a bug.
My impression is that all participants of this thread agree that it is a bug. > Doing m == m1, should first coerce both to > SR, then compare there. That's already the case. > Comparison there is supposed to currently > return true only if we can prove the two things are equal -- otherwise > false Correct, but in the current example SageMath behaves differently. I just tried to come up with different examples exposing the buggy behaviour, but failed. For example: sage: R = RealField(1000) sage: a = ZZ(floor(R(sqrt(2))*2^100)) sage: a.n() == (2^100*sqrt(2)).n() True sage: bool(a==2^100*sqrt(2)) False So, why does SageMath give a correct answer in my example, but a wrong answer in David's example? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
