-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Modernize to default constructor and nullptr in torch #61735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Differential Revision: D29716659 fbshipit-source-id: d2967212d00ddfb8dce2892cfe2ac45241296ace
💊 CI failures summary and remediationsAs of commit 7e70b32 (more details on the Dr. CI page and at hud.pytorch.org/pr/61735):
🕵️ 1 new failure recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
This pull request was exported from Phabricator. Differential Revision: D29716659 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no such thing is tp_vectorcall_offset
0, /* tp_itemsize */ | ||
nullptr, /* tp_dealloc */ | ||
// NOLINTNEXTLINE(modernize-use-nullptr) | ||
0, /* tp_vectorcall_offset */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Item after tp_dealloc
is tp_print
, isn't it?
https://github.com/python/cpython/blob/0a0a135bae2692d069b18d2d590397fbe0a0d39a/Include/object.h#L353-L354
0, /* tp_vectorcall_offset */ | |
nullptr, /* tp_print */ |
Actually, see https://docs.python.org/3/c-api/typeobj.html#c.PyTypeObject.tp_vectorcall_offset |
This pull request has been merged in 349f2f7. |
Differential Revision: D29716659