cpp-coding-standards

Comprehensive coding standards for modern C++ (C++17/20/23) derived from the C++ Core Guidelines . Enforces type safety, resource safety, immutability, and clarity. These themes recur across the entire guidelines and form the foundation: Before marking C++ work complete: - Writing new C++ code (classes, functions, templates) - Reviewing or refactoring existing C++ code - Making architectural decisions in C++ projects - Enforcing consistent style across a C++ codebase - Choosing between language features (e.g., enum vs enum class , raw pointer vs smart pointer) - Non-C++ projects - Legacy C codebases that cannot adopt modern C++ features - Embedded/bare-metal contexts where specific guidelines conflict with hardware constraints (adapt selectively) - RAII everywhere (P.8, R.1, E.6, CP.20): Bind resource lifetime to object lifetime - Immutability by default (P.10, Con.1-5, ES.25): Start with const / constexpr ; mutability is the exception - Type safety (P.4, I.4, ES.46-49, Enum.3): Use the type system to prevent errors at compile time - Express intent (P.3, F.1, NL.1-2, T.10): Names, types, and concepts should communicate purpose - Minimize complexity (F.2-3, ES.5, Per.4-5): Simple code is correct code - Value semantics over pointer semantics (C.10, R.3-5, F.20, CP.31): Prefer returning by value and scoped objects - Returning T&& from functions (F.45) - Using va_arg / C-style...