cpp-development

Follow a five-step workflow: analyze build flags and standard version, design interfaces with C++20 concepts, implement with RAII and smart pointers, verify with AddressSanitizer and UBSan, then optimize only after profiling with perf or callgrind.

Use std::make_unique for default single ownership and std::make_shared only when shared ownership is genuinely required. Raw pointers should appear solely as non-owning observers in function parameters.

Rule of Zero means composing from resource-managing types so the compiler generates all special members. Rule of Five applies when a class owns a raw resource directly, requiring you to define or delete the destructor, copy, and move operations.

Yes, constraining templates with concepts like std::integral or custom requires-expressions produces clear diagnostics at the call site instead of deep instantiation errors. For pre-C++20 code, static_assert serves as the fallback.

An unnamed lock_guard like std::lock_guard<std::mutex>(m) creates a temporary destroyed immediately, releasing the lock. Always name the variable, e.g. std::lock_guard<std::mutex> lk{m}, so it lives until scope exit.

No, volatile only prevents compiler reordering and provides no CPU memory-ordering guarantees. Use std::atomic<T> or mutexes with RAII locks for correct inter-thread synchronization.