Message136468
| Author |
mark.dickinson |
| Recipients |
alex, belopolsky, daniel.urban, mark.dickinson, pitrou, rhettinger |
| Date |
2011年05月21日.19:32:27 |
| SpamBayes Score |
9.7635975e-06 |
| Marked as misclassified |
No |
| Message-id |
<1306006347.99.0.00190259995193.issue11986@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> keep naive implementation of builtin max()
Agreed.
> provide symmetric float.max such that nan.max(x) = x.max(nan) = x (nan
> result would be a valid but less useful alternative.)
That might be viable (a math module function might also make sense here), though it feels a bit YAGNI to me. If we were going to add such a method, it should follow IEEE 754: nan.max(x) == x.max(n) == x, but also nan.min(x) == x.min(nan) == x, for finite x. (See section 5.3.1.) |
|