Daniel Colascione <[email protected]> added the comment: On Sun, Oct 1, 2017 at 2:01 PM, Antoine Pitrou <[email protected]> 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? ---------- _______________________________________ Python tracker <[email protected]> <https://bugs.python.org/issue31654> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
