ENH: size() to return None on dask instead of nan #231
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.
dask arrays of unknown shape return NaN in their
.size
and.shape
properties. This was chosen a long time before the Array API standard existed, but alas diverges from the array API standard itself:ndonnx, another library which can have arrays of unknown shape, uses None instead.
This PR changes the
size()
function to make dask conform to the standard and adds units tests which were previously missing.Q: Should we add a
shape()
function to cover for Dask's.shape
property non-standard behaviour?