-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
Use standard integer types instead of Python aliases #15659
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
Should we leave this for compatibility? Lines 73 to 78 in 132acab
|
/* 64bit platforms with unsigned int64 */ | ||
typedef PY_UINT64_T UINT64; | ||
typedef unsigned char UINT8; | ||
typedef uint64_t UINT64; |
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.
Probably we can remove these typedef
s and restore the original ones?
cpython/Modules/_sha3/kcp/KeccakP-1600-opt64.c
Lines 21 to 24 in 132acab
#if NOT_PYTHON | |
typedef unsigned char UINT8; | |
/* typedef unsigned long long int UINT64; */ | |
#endif |
You can always open a new issue and then reference the old issue in the description. :-) |
It's just that I noticed a few remainaing PY_INT64_T types while working on https://bugs.python.org/issue40302 |
I'd attribute this to the old issue, but for some reason, some developers seem to be annoyed by using old issues.