CurtHagenlocher commented on issue #97: URL: https://github.com/apache/arrow-dotnet/issues/97#issuecomment-3372484307
There's definitely a tension between wanting to expose low-level details for flexibility in consumption and wanting to hide them for flexibility in implementation. But I suspect we're already at a place where the exposed details make it hard to support buffers > 2GB or a more flexible ownership scheme that would allow for sophisticated sharing through the C API. Exposing the `IMemoryOwner`-based constructor likely wouldn't make those any more difficult. -- 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]
