What are the best practices for using custom allocators in C++11?

What are the best practices for using custom allocators in C++11?

When using custom allocators in C++11, it's important to ensure they are exception-safe, efficient, and compatible with standard containers.

Can you explain what exception-safe means in this context?

Sure! Exception-safe means that your allocator should not leave the program in an invalid state if an exception occurs during memory allocation or deallocation.

What are some common pitfalls to avoid with custom allocators?

Common pitfalls include not handling memory alignment properly, failing to account for the allocator's state after an exception, and not adhering to the allocator's requirements for the types it manages.

How can I test my custom allocator?

You can test your custom allocator by using it with standard containers and checking for memory leaks, performance, and exception safety through various test cases.