cpp-coding-standards

Use the quick-reference checklist covering raw new/delete elimination, const-correctness, enum class usage, nullptr, explicit constructors, and RAII locks. Each checklist item references a specific Core Guidelines rule number for traceability during review.

The guidelines target modern C++ including C++17, C++20, and C++23. Features like concepts, std::scoped_lock, std::string_view, and constexpr computation are covered alongside foundational rules from the C++ Core Guidelines.

Prefer std::unique_ptr by default since it expresses exclusive ownership with zero overhead (rule R.21). Use std::shared_ptr only when ownership is genuinely shared, and always create shared pointers with std::make_shared (R.22).

Prefer enum class over plain enum (rule Enum.3) because it is strongly typed and does not leak enumerator names into the enclosing scope. Avoid ALL_CAPS enumerator names (Enum.5) and unnamed enumerations (Enum.6).

They do not apply to non-C++ projects or legacy C codebases that cannot adopt modern C++ features. In embedded or bare-metal contexts where guidelines conflict with hardware constraints, adopt rules selectively rather than wholesale.

Use std::scoped_lock to acquire multiple mutexes atomically in a deadlock-free manner (rule CP.21). Always use RAII lock wrappers like lock_guard or unique_lock with names (CP.20, CP.44), and never call unknown code while holding a lock (CP.22).