pixelherodev commented on PR #322: URL: https://github.com/apache/arrow-go/pull/322#issuecomment-3513797047
It sounds like the best option that doesn't break anything for anyone, while still getting at least _most_ of the benefits, is to add a build flag to switch from retain/release to AddCleanup, and then to move the cleanup logic into the Allocators, so that anyone using the GoAllocator has no additional runtime overhead for memory management? We can always try and revisit later and figure out a solution for non-Go use cases.. -- 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]
