RetroSearch Browse

Fri Aug 26 01:31:02 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-August/113098.html

On Wed, Aug 24, 2011 at 10:50 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> Not with these words, though. As I recall, it's rather like (still
> with different words) "len() will stay O(1) forever, regardless of
> any perceived incorrectness of this choice".

And indexing/slicing will also be O(1).

> An attempt to change
> the builtins to introduce higher complexity for the sake of correctness
> is what he rejects. I think PEP 393 balances this well, keeping
> the O(1) operations in that complexity, while improving the cross-
> platform "correctness" of these functions.

+1, I am comfortable with the balance struck by the PEP.

-- 
--Guido van Rossum (python.org/~guido)

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

Showing content from https://mail.python.org/pipermail/python-dev/2011-August/113098.html below:

[Python-Dev] PEP 393 Summer of Code Project