[Python-Dev] New poll about a macro for safe reference replacing
Serhiy Storchaka
storchaka at gmail.com
Wed Dec 23 09:50:21 EST 2015
More information about the Python-Dev mailing list
Wed Dec 23 09:50:21 EST 2015
- Previous message (by thread): [Python-Dev] New poll about a macro for safe reference replacing
- Next message (by thread): [Python-Dev] New poll about a macro for safe reference replacing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 22.12.15 18:36, Meador Inge wrote: > On Tue, Dec 22, 2015 at 3:58 AM, Serhiy Storchaka <storchaka at gmail.com > <mailto:storchaka at gmail.com>> wrote: > > On 21.12.15 23:57, Steve Dower wrote: > > Was Py_MOVEREF (or MOVE_REF) ever suggested? > > > This would be nice name. The macro moves the ownership. But I think > it's too late. Otherwise we'll never finish the bikeshedding. > > > FWIW, I like this name the best. It is increasingly popular for > languages to talk about moving ownership (e.g. move semantics in C++, > Rust, etc...). Oh, I'm confused. Should I make a new poll? With new voters Py_MOVEREF can get more votes than Py_SETREF.
- Previous message (by thread): [Python-Dev] New poll about a macro for safe reference replacing
- Next message (by thread): [Python-Dev] New poll about a macro for safe reference replacing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list