Creational Design Patterns in Modern C++ - Generic Pool - Part II

The video tutorial covers the no discard attribute in C-17, emphasizing its role in ensuring return values are stored. It discusses making classes thread-safe using mutexes and handling private constructors in object pools. The tutorial introduces default allocators, allowing customization of object allocation and deallocation. It explains the concept of growable and non-growable pools, with size specified at compile time. The strategy pattern is highlighted for its flexibility in customizing object pool behavior without altering the class itself.

What considerations should be made for thread safety in an object pool?

Describe how the object pool can be made non-growable and the implications of this.

What is the significance of the allocator being a strategy in the context of the object pool?