💥 concrete complex scalar types #391
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jorenham
added
stubs: Incorrect
numpy.generic
is: Breaking
jorenham
force-pushed
the
concrete-complex-scalars
branch
from
ad7919f to
5c82242
Compare
This was referenced Mar 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
backwards incompatible bugfixes:
complex192andcomplex256are now (equivalent) aliases ofclongdoubleclongdouble.item()and.tolist()now correctly returnsclongdoubleinstead ofbuiltins.complexcomplex64andclongdoublehave been made into propercomplexfloatingsubtypes__complex__and__hash__definitions fromcomplexfloatingto its concrete subtypestowards #198
towards #136