Message274234
| Author |
skrah |
| Recipients |
asvetlov, pitrou, scoder, serhiy.storchaka, skrah, vstinner |
| Date |
2016年09月02日.11:45:24 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1472816724.96.0.659959624905.issue22458@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I've left comments on GitHub.
[scoder]
> As I said, where ever exact calculations are needed..
Even if the formatting comment is addressed, the main problem with
this benchmark is that *both* fraction and decimal calculations
are in fact exact here.
You can check that by printing out the values for "t" in the loop
like I suggested on GitHub.
This is of course one of the main features of Decimal: If you're
willing to take the penalty of a large precision, calculations
can often be exact; similar to taking the penalty of potentially
huge numerators and denominators in fractions.
So this benchmark cannot be used to show the superiority of exact
fractions. |
|