Creational Design Patterns in Modern C++ - Meyer's Singleton

The video tutorial discusses the challenges of locking in programming, particularly when accessing instance variables outside critical sections. It introduces the Meyers Singleton, a solution for double-check locking, which is thread-safe from C++11 onwards. The tutorial compares eager and lazy instance creation for Singleton classes, advising on when to use each based on thread safety and runtime data needs. The Meyers Singleton is recommended for its thread safety and ease of use.

What is a key advantage of using a lazy instance in the Mayor Singleton pattern?

• It is only created when needed.

• It requires manual deletion.

• It is stored on the heap.

• It is created at program startup.

From which version of C++ is static construction considered thread safe?

• C++17

• C++11

• C++03

• C++98

What might be necessary in C++98 to ensure a single instance is created in a thread-safe manner?

• Implementing a custom memory allocator

• Using a different programming language

• Relying on compiler optimizations

• Utilizing operating system APIs

Why might you choose an eager instance over a lazy instance for a Singleton class?

• It allows runtime data initialization.

• It is more memory efficient.

• It is easier to debug.

• It is always thread safe.

What is a benefit of using the Mere Singleton pattern?

• It requires manual memory management.

• It is only suitable for single-threaded applications.

• It is not thread safe.

• It can be initialized with runtime data.