philwave at gmail.com
Fri May 17 11:36:43 CEST 2019
>Please watch one of Lakos' recent allocator's talks for a ton of benchmarks how a custom
> allocator helps speed up - not just std::vector but also std::map, if
> one is so inclined.
I fully agree with this topic (and kudos for Lakos in general).
That's actually a lack in Qt containers: no allocation customization
Allocators help a lot, but when it's a matter of maps, there are many
other aspects coming into play.
> While it is true that there's no such container, it's even more true
> that there will never be one. Because C++ made the allocators, which
> back in the 90s were just a way to handle near and far pointers on older
> architectures, fit for actually abstracting allocation.
I don't know why you say there will never be such a standard allocator.
For example, eastl has such a container with custom allocator:
There is also a recent c++ proposal:
BTW, this article fails to mention a recent excellent contribution from google
> There is no readability difference between the use of a Qt container
> and that of an STL container.
I have a different opinion of this. And this is what I mean when I say
that Qt containers are convenient.
More information about the Development