RetroSearch Browse

Mon Oct 11 02:15:08 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-October/104627.html

2010/10/10 Antoine Pitrou <solipsis at pitrou.net>:
> Personnally, I'm not convinced that a maximum 25% improvement on a
> rather uncommon use case (min() and max() on a sequence of objects
> which take a long time to compare) is a compelling argument for a
> builtin.  On the other hand, it would be a rather simple and intuitive
> builtin, so why not?

Because new builtins should have a better reason that there's no good
reason not to. :)

-- 
Regards,
Benjamin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-October/104627.html below:

[Python-Dev] [Python-ideas] minmax() function returning (minimum, maximum) tuple of a sequence