➜

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 vstinner
Recipients nascheme, vstinner
Date 2020-02-07.09:55:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1581069312.55.0.751550692654.issue39573@roundup.psfhosted.org>
In-reply-to
Content 
Would a Py_TYPE_IS() macro help code readability?

For example:
    #define Future_CheckExact(obj) (Py_TYPE(obj) == &FutureType)
would become:
    #define Future_CheckExact(obj) (Py_TYPE_IS(obj, &FutureType))

Py_TYPE_IS() would be more efficient for tagged pointers.

I'm not sure about the macro name. Neil used Py_IS_TYPE(obj, type).

Note: Py_TYPE_EQ(obj, type) name sounds confusing since the first parameter is an object, whereas the second one is a type.
History
Date User Action Args
2020-02-07 09:55:12vstinnersetrecipients: + vstinner, nascheme
2020-02-07 09:55:12vstinnersetmessageid: <1581069312.55.0.751550692654.issue39573@roundup.psfhosted.org>
2020-02-07 09:55:12vstinnerlinkissue39573 messages
2020-02-07 09:55:12vstinnercreate