RetroSearch Browse

Sat Aug 27 02:17:18 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-August/113160.html

Paul Moore wrote:

> IronPython and Jython can retain UTF-16 as their native form if that
> makes interop cleaner, but in doing so they need to ensure that basic
> operations like indexing and len work in terms of code points, not
> code units, if they are to conform. ... They lose the O(1)
> guarantee, but that's easily defensible as a tradeoff to conform to
> underlying runtime semantics.

I would only agree as long as it wasn't too much worse
than O(1). O(log n) might be all right, but O(n) would be
unacceptable, I think.

-- 
Greg

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

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

[Python-Dev] PEP 393 Summer of Code Project