kkraus14 commented on issue #38325: URL: https://github.com/apache/arrow/issues/38325#issuecomment-2021049805
Are there cases where we need zero copy regardless of going across devices? * Do we ever want to support mutating memory via these interfaces? If so, we don't have a clear way to guarantee we don't mutate a copy. * If a consumer has the ability to generically handle both array-like things and dataframe-like things, it makes it a bit harder to implement efficiently. I.E. I might want to write something that has a flow like "try to get arrow zero copy, fall back to dlpack zero copy, fall back to arrow copy, fall back to dlpack copy". Assuming we make copies implicit via `__arrow_c_array__`, this makes the only copy we'll support handling is device --> CPU for now. What would addressing along more generic copy requests later look like? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
