Custom allocator basics
The magic behind dynamic memory management in std::vector (and many other STL containers) lies in a component that might not immediately catch your attention: the allocator. At its core, an allocator serves as an interface, abstracting the memory source for the container. This abstraction ensures that the container, like our trusty std::vector, can function without being tethered to a specific memory source or allocation strategy.
The role and responsibility of an allocator
Allocators are the unsung heroes of memory management. They handle allocating and deallocating memory chunks, thus ensuring that our data structures grow and shrink gracefully. Beyond these tasks, allocators can also construct and destroy objects. They bridge the gap between raw memory operations and higher-level object management.
But why do we need such an abstraction? Why not simply use the new and delete operations? The answer lies in flexibility. The STL empowers developers...
