pitrou commented on issue #28: URL: https://github.com/apache/arrow-go/issues/28#issuecomment-3319995638
> I don't think you can (or would want to) add requirements like that post-facto. Well, we can make it a recommendation rather than a requirement. It's quite common for specifications to be refined over time, without needing to claim a new version number. > I really think the onus is on the Go FFI implementation to make sure they can handle zero-length slices correctly without tripping up the garbage collector. Perhaps, but I'd be curious about the implementation difficulty for Go vs. Polars to solve this interoperability issue. @zeroshade Would it be easy to fix on the Go side? -- 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]
