Just use None
for strides
in DeviceBuffer
#477
Merged
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.
Originally there were some issues in CuPy and Numba with how they implemented
__cuda_array_interface__
and handled other objects that supported it where they couldn't handlestrides
ofNone
cleanly. So we addedstrides
here with what it should be. However both libraries have since cleaned this up ( CuPy 6.6.0+, cupy/cupy#2669 and Numba 0.46.0+, numba/numba#4609 ) and we require newer versions of both. As some code contains fast paths whenstrides
isNone
, switch to usingNone
here as we ensure contiguous data inDeviceBuffer
s. This should allow us to take advantage of those fast paths where possible.