Movatterモバイル変換

[Python-Dev] Internal representation of strings and Micropython

• Previous message:[Python-Dev] Internal representation of strings and Micropython
• Next message:[Python-Dev] Internal representation of strings and Micropython
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

On 4 June 2014 11:17, Steven D'Aprano <steve at pearwood.info> wrote:> My own feeling is that O(1) string indexing operations are a quality of> implementation issue, not a deal breaker to call it a Python.If string indexing & iteration is still presented to the user as "anarray of code points", it should still avoid the bugs that plaguedboth Python 2 narrow builds and direct use of UTF-8 encoded Py2strings.If they don't try to offer C API compatibility, it should be feasibleto do it that way. If they *do* try to offer C API compatibility, theymay have a problem.> I can't> see any requirement in the docs that str[n] must take O(1) time, but> perhaps I have missed something.There's a general expectation that indexing will be O(1) because allthe builtin containers that support that syntax use it for O(1) lookupoperations.Cheers,Nick.-- Nick Coghlan   |ncoghlan at gmail.com   |   Brisbane, Australia

• Previous message:[Python-Dev] Internal representation of strings and Micropython
• Next message:[Python-Dev] Internal representation of strings and Micropython
• Messages sorted by:[ date ][ thread ][ subject ][ author ]