pitrou commented on issue #28: URL: https://github.com/apache/arrow-go/issues/28#issuecomment-3319749837
> [@pitrou](https://github.com/pitrou) might this have implications for arrow-cpp too? (I suppose arrow-cpp would always ignore the pointer when the allocation is 0-length, though, so there should be no problem.) I don't think we would do anything with the pointer, so I don't think so. > I don't really see how this is a Polars issue to be honest. Strictly speaking, it's not (the C Data Interface spec does not prohibit it), but Polars isn't being a very good citizen either by passing a pointer that it doesn't own. We could actually strength the requirement for pointers in the C Data Interface spec, because it seems otherwise that can trip up Go (and perhaps other garbage-collected languages?). -- 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]
