API: Remove PyArray_GetCastFunc
and any guarantee that ->castfuncs
are defined
#25161
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.
NumPy never used them internally, in two places, we did expose access to these functions indirectly. (In these places use the cast function also used in
PyArray_Pack()
.)We still do support the use for custom legacy dtype and some casts were never ported to the newer machinery, thus, those need to remain.
The second commit tries to remove all cast functions we do not use internally.
I think we need to delete this, pandas has one useless occurrence of this. If anyone complains or has doubts, I would be happy to introduce a
PyArray_CastContiguous(...)
(or evenPyArray_CastBuffer
which is strided) with a backport implementation that keeps using these on old versions (because fetching the real one needs a bit of magic).Cleaning out
arraytypes.c.src
to not include the unnecessary versions is unfortunately a bit of a mess/reorg :(.