You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See the discussion around numpy/numpy#19083 (comment). We should make it clear that any library is free to implement __dlpack__ and __dlpack_device__, and from_dlpack() can return a non-array-API-complaint object.
Ideally, the second half of this page https://data-apis.org/array-api/latest/design_topics/data_interchange.html should not live in the array API standard, but instead in DLPack's website so that we can simply link to it. Unfortunately DLPack doesn't seem to plan on creating a website in the near future, so perhaps we can add a big warning mark during the rewriting planned in #185?
The text was updated successfully, but these errors were encountered:
See the discussion around numpy/numpy#19083 (comment). We should make it clear that any library is free to implement
__dlpack__
and__dlpack_device__
, andfrom_dlpack()
can return a non-array-API-complaint object.Ideally, the second half of this page https://data-apis.org/array-api/latest/design_topics/data_interchange.html should not live in the array API standard, but instead in DLPack's website so that we can simply link to it. Unfortunately DLPack doesn't seem to plan on creating a website in the near future, so perhaps we can add a big warning mark during the rewriting planned in #185?
The text was updated successfully, but these errors were encountered: