cpp-coding-standards

Use a rule-referenced checklist mapping each guideline section (R for resources, C for classes, ES for expressions) to concrete DO and DON'T examples. Check for raw new/delete, missing const, plain enums, and unconstrained templates against rules like R.11, Con.1, Enum.3, and T.10.

Rule of Zero (C.20) means letting the compiler generate all special members by using value types and smart pointers. Rule of Five (C.21) applies when you manage a resource directly: if you define any of destructor, copy, or move operations, you must define all five.

Prefer unique_ptr by default (R.21) since it has zero overhead and expresses exclusive ownership clearly. Use shared_ptr only when ownership is genuinely shared, and create it with make_shared (R.22). Raw pointers should represent non-owning observers only (R.3).

Not fully. The guidelines target modern C++17/20/23 and explicitly exclude legacy C codebases that cannot adopt modern features. Embedded or bare-metal contexts with hardware constraints should adapt the rules selectively rather than applying them wholesale.

Volatile (CP.8) does not provide atomicity or memory ordering guarantees; it only prevents compiler optimization of accesses, making it suitable for hardware I/O only. Use std::mutex with RAII locks like scoped_lock or lock_guard, or std::atomic, for correct synchronization.