Golang doesn't have copy elison unlike C++ so in principle you need to leverage the heap escape anyways.
Golang's arenas were an experiment that has already been ditched by the maintainer as un-feasible.
> Golang doesn't have copy elison unlike C++ so in principle you need to leverage the heap escape anyways.
I mean you can pass structs by ref or value around, which makes direct impact will they be on stack or heap.
> Golang's arenas were an experiment that has already been ditched by the maintainer as un-feasible.
Thank you, good to know, looks like big pros in favor of rust as lang for my next project.
also, golang has arena API now, and it also makes heap allocations super cheap if you manage to integrate it into app life cycle.