docs: clarify that behavior when provided a nested sequence to asarray
is unspecified
#917
+4
−0
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.
This came up in data-apis/array-api-strict#118.
AFAICS, the behavior of
asarray([array, list])
does vary by implementation and is not explicitly mentioned in the standard. Thus add a note that it's unspecified.Due diligence:
CuPy : allows sequences of arrays, does not allows mixed sequences of arrays/scalars:
Torch: does not allow sequences of tensors
JAX : allows sequences but not scalars
Dask.array: as JAX.