A deep dive into the Go memory allocator and garbage collector

Re:A deep dive into the Go memory allocator and garbage coll... by netheril96 on Friday August 31, 2018 @07:17AM (#17884562)

In C++ if the class has non-trivial constructors, neither stack nor heap allocations are free. So in C++ reusing objects is still often better for performance.

[ Parent | on HN ]

Re:A deep dive into the Go memory allocator and garbage coll... by guipsp on Friday August 31, 2018 @10:11AM (#17885713)

I'd argue that if your constructors/destructors are non-trivial, then reusing objects is also often non-trivial.

[ Parent | on HN ]