On 2014-10-07 17:45, Nils Bruin wrote:
Another conclusion one can draw from that is that floats got modelled
wrong: that precision is a property of the element, not the parent.
That cannot really work, since we really want RealField(100)(1/3) to be
different from RealField(53)(1/3)
That's a very deep change.
Actually, I don't think it is. In fact, for almost all parents, nothing
would change.
I am strongly -1 to introducing something
like that without very strong evidence that this is important in
practice (which I doubt).
Fair enough. I don't particularly need this feature, but I do think the
proposal makes sense, is quite simple and easy to implement.
The ramifications for coercion discovery are also quite big:
No, you're understanding it wrong. The parent of the result of any
computation would be the same as now. The result of adding 2 RealNumbers
with differing precision would still be a RealNumber of the lowest
precision.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
