3 ms·
> putting each C++ object into its own heap allocation behind a smart pointer, creating and destroying tiny objects all the time Are C++ allocators so bad that
by lmm 3y ago
> putting each C++ object into its own heap allocation behind a smart pointer, creating and destroying tiny objects all the time
Are C++ allocators so bad that they can't handle this use pattern? Yes, you can make a bunch of manual effort to use the allocator less, but you shouldn't have to.