Skip to content
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

Add recommendation on what to do with DLPack read-only flag #749

Merged
merged 1 commit into from
Feb 16, 2024

Commits on Feb 15, 2024

  1. Add recommendation on what to do with DLPack read-only flag

    This is a follow-up to the discussion in data-apisgh-191. It's a recommendation
    rather than a hard requirement to allow implementers some choice.
    That said, this is how things worked in practice before DLPack 1.0
    as well, since there was no flag to represent read-only. Experience
    with JAX showed that exposing shared memory was preferred by users
    over raising or always making a copy of the data on the producer side.
    rgommers committed Feb 15, 2024
    Configuration menu
    Copy the full SHA
    11cbc07 View commit details
    Browse the repository at this point in the history