Skip to content

Document the mutability assumptions for the interop protocol #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rgommers opened this issue Aug 25, 2021 · 0 comments
Open

Document the mutability assumptions for the interop protocol #56

rgommers opened this issue Aug 25, 2021 · 0 comments
Labels
documentation Improvements or additions to documentation interchange-protocol

Comments

@rgommers
Copy link
Member

This was just asked about at https://twitter.com/__AlexMonahan__/status/1430522318854377475. I'd say we should have a similar argument as https://data-apis.org/array-api/latest/design_topics/copies_views_and_mutation.html. We cannot prevent mutations in the protocol itself, and existing libraries already may have APIs that do mutate in-place. So we should recommend against it (but of course power users that really understand what they are doing could go right ahead and mutate to their hearts' content - this is the same as for the buffer protocol, DLPack et al.).

There's an earlier discussion at #10 (which was unrelated to the protocol). The general sentiment was that in-place operations must be avoided for a full dataframe API.

Right now https://data-apis.org/dataframe-protocol/latest/ says nothing about mutability, this should be added.

@rgommers rgommers added documentation Improvements or additions to documentation interchange-protocol labels Aug 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation interchange-protocol
Projects
None yet
Development

No branches or pull requests

1 participant