➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Daniel Colascione
Recipients Daniel Colascione, amaury.forgeotdarc, belopolsky, davin, meador.inge, pitrou, rhettinger, serhiy.storchaka
Date 2017-10-01.21:35:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAKOZuetnjcnShhbe5AzxBw0MYdb0DdXE0fZ_Y5vyRRQ+UuqkLQ@mail.gmail.com>
In-reply-to <d27f1fec-9395-9917-2fb0-bbe63fb16edb@free.fr>
Content 
On Sun, Oct 1, 2017 at 2:01 PM, Antoine Pitrou <report@bugs.python.org>
wrote:

> Perhaps other core developers will disagree with me and agree to include
> (i.e. review, maintain) this functionality.  I simply am not convinced
> it deserves being included, but that's not a veto.

ctypes is a library for operating on native memory and working with native
functions. Performing atomic operations on memory is definitely within its
scope. Why does ctypes include memmove? Why memmove and not
compare-and-exchange? What evidence, if any, would convince you?
History
Date User Action Args
2017-10-01 21:35:18Daniel Colascionesetrecipients: + Daniel Colascione, rhettinger, amaury.forgeotdarc, belopolsky, pitrou, meador.inge, serhiy.storchaka, davin
2017-10-01 21:35:18Daniel Colascionelinkissue31654 messages
2017-10-01 21:35:18Daniel Colascionecreate