The std::_Container_proxy going through the allocator alot. On the MSVC this causes alot of memory allocations. I am not sure at the moment how this is going to be on gcc or other compilers/platforms.
Maybe we can ease that experience a little bit because this class uses memory even on local std containers.
I can't very much believe it but this code performs heap allocations through a custom allocator.
motor::string_t test ;
motor::vector< int > test_v ;
The constructor causes the allocator to trigger an allocation of the aforementioned std::_Container_proxy. Maybe I missed something in the allocator that needs to be done?
The
std::_Container_proxygoing through the allocator alot. On the MSVC this causes alot of memory allocations. I am not sure at the moment how this is going to be on gcc or other compilers/platforms.Maybe we can ease that experience a little bit because this class uses memory even on local std containers.
I can't very much believe it but this code performs heap allocations through a custom allocator.
The constructor causes the allocator to trigger an allocation of the aforementioned
std::_Container_proxy. Maybe I missed something in the allocator that needs to be done?