A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2017-September/149127.html below:

[Python-Dev] Inplace operations for PyLong objects

[Python-Dev] Inplace operations for PyLong objects [Python-Dev] Inplace operations for PyLong objectsChris Barker chris.barker at noaa.gov
Fri Sep 1 16:05:12 EDT 2017
On Thu, Aug 31, 2017 at 5:12 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:

> I'm skeptical there are some programs out there that are limited by the
> speed of PyLong inplace additions.
>

indeed, but that could be said about any number of operations.

My question is -- how can the interpreter know if it can alter what is
supposed to be an immutable in-place? If it's used only internally to a
function, the it would be safe, but how to know that?

-CHB



-- 

Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20170901/b95082df/attachment.html>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4