GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [Python-Dev] Slice as a copy... by design?
  • [Python-Dev] Slice as a copy... by design?
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Slice as a copy... by design?

[Python-Dev] Slice as a copy... by design?

Guido van Rossum guido at python.org
Thu May 22 19:37:06 CEST 2008

  • Previous message: [Python-Dev] Slice as a copy... by design?
  • Next message: [Python-Dev] Slice as a copy... by design?
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, May 22, 2008 at 10:01 AM, Aahz <aahz at pythoncraft.com> wrote:
> On Thu, May 22, 2008, Facundo Batista wrote:
>>
>> A thread in PyAr raised the question that, considering that strings
>> are immutable, why a slice of a string is a copy and not a reference
>> to a part of that string.
>
> Someone did a patch for this at one point, but I don't remember what
> happened.

I rejected it because I came up with a worst-case scenario where the
behavior with the patch in place was much, much worse than the
behavior without it -- improved performance in other scenarios
notwithstanding.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

  • Previous message: [Python-Dev] Slice as a copy... by design?
  • Next message: [Python-Dev] Slice as a copy... by design?
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.