Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
gh-61103: support double complex (_Complex) type in ctypes #120894
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
gh-61103: support double complex (_Complex) type in ctypes #120894
Changes from all commits
c9b872f
b402300
ad39e6d
fd9135b
c296fb3
7453ca5
e444c9c
2e90643
32ffacf
9163950
bf81682
af2fdce
6d9d5ab
f9c709c
ccd418d
eb313dc
693c04e
0ee7049
de91bbe
b79200e
be6a685
04e89c2
0bc87da
6347412
e757fb6
1eb989c
b44aae2
2153608
af42aa8
e57198e
36732bc
892b241
ee953c3
875cbb8
f8e3a47
f447919
7b1c366
2ea028a
837add4
1b8f37e
0bd1ebe
6eba445
a6ac463
615e8de
f7d9973
3d170bd
4dd044c
4cf7045
264fa7d
f54b964
23db200
5a7e366
388e2ca
e888565
56b524c
e9cab4a
6d5bf66
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 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.
Here I would like to emphasize where new macro create a problem. I.e. name - matter, what it's - actually irrelevant.
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.
Can we avoid the relative include? They tend to produce problems further down the road.
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.
How about
Include/internal/pycore_pycomplex.h
?There is
Include/internal/pycore_pymath.h
, that (IMHO) does part of workModules/_math.h
(<math.h>
workarounds). There are no relative includes of_math.h
(yet), but I think these files could be merged.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.
I feel that
_math.h
and_complex.h
could be named asInclude/internal/pylibc_{math,complex}.h
because what they do is patching the C standard library itself rather than adding new functionalities (well, for_complex.h
it's not really a patch but rather a way to harmonize the calls).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.
@vstinner: I'd really like to avoid the relative include, but we can fix that in a follow-up PR.