zeroshade commented on issue #62: URL: https://github.com/apache/arrow-go/issues/62#issuecomment-5501440552
Closing this one out. Three years on, the concern @spenczar raised in https://github.com/apache/arrow-go/issues/62#issuecomment-2319657465 turned out to be the deciding factor: arenas never graduated out of `GOEXPERIMENT=arenas`, the proposal (golang/go#51317) remains on hold, and the Go team's guidance is still that the API may change or be removed without warning. Building an arena-backed `memory.Allocator` into arrow-go would mean shipping a public surface gated on an experiment that we can't promise will exist in the next Go release, so I don't think it's something we should take on speculatively. If arenas are ever unfrozen with a committed API, this is absolutely worth revisiting — an arena `memory.Allocator` remains the natural first integration point, and the benchmarks in the repo are still the right way to evaluate it. Happy to reopen at that point. Thanks @ivanmemruk for raising it and @spenczar for the early heads-up. -- 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]
