Modern Cpp

by trailofbits82fe82262526No license7.4K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated yesterday

Guides C++ code toward modern idioms (C++20/23/26). Use when writing new C++ code, modernizing legacy patterns, or working on security-critical C++. Replaces raw pointers with smart pointers, SFINAE with concepts, printf with std::print, error codes with std::expected.

Instructions onlySoftware Development Security

AI-generated overview

Guides C++ code toward modern C++20/23/26 idioms, replacing legacy patterns and adding compiler hardening.

What it does: This skill provides guidance for writing and modernizing C++ code using C++20, C++23 and C++26 idioms. It presents anti-pattern replacement tables, a decision tree, feature tiers ranked by practical usability, compiler hardening flags, sanitizer recommendations and a best-practices checklist. It also points to reference documents covering anti-patterns, standard features and safe idioms.
When to use it: Use it when writing new C++ functions, classes or libraries, when modernizing pre-C++20 code, when choosing between legacy and modern approaches, or when working on security-critical C++. It is not intended for pure C code, build system configuration, or projects where an older standard is explicitly required.
Requirements: No scripts; instructions and reference documents only. It assumes a C++ toolchain and, for the hardening guidance, compilers such as GCC or Clang plus sanitizers, but it does not itself install or run anything.

Modern C++

Guide for writing modern C++ using C++20, C++23, and C++26 idioms. Focuses on patterns that eliminate vulnerability classes and reduce boilerplate, with a security emphasis from Trail of Bits.

When to Use This Skill

Writing new C++ functions, classes, or libraries
Modernizing existing C++ code (pre-C++20 patterns)
Choosing between legacy and modern approaches
Working on security-critical or safety-sensitive C++
Reviewing C++ code for modern idiom adoption

When NOT to Use This Skill

User explicitly requires older standard: Respect constraints (embedded, legacy ABI)
Pure C code: This skill is C++-specific
Build system questions: CMake, Meson, Bazel configuration is out of scope
Non-C++ projects: Mixed codebases where C++ isn't primary

Anti-Patterns to Avoid

Avoid	Use Instead	Why
`new`/`delete`	`std::make_unique`, `std::make_shared`	Eliminates leaks, double-free
Raw owning pointers	`std::unique_ptr`, `std::shared_ptr`	RAII ownership semantics
C arrays (`int arr[N]`)	`std::array<int, N>`	Bounds-aware, value semantics
Pointer + length params	`std::span<T>`	Non-owning, bounds-checkable
`printf` / `sprintf`	`std::format`, `std::print`	Type-safe, no buffer overflow
C-style casts `(int)x`	`static_cast<int>(x)`	Explicit intent, auditable
`#define` constants	`constexpr` variables	Scoped, typed, debuggable
SFINAE / `enable_if`	Concepts + `requires`	Readable constraints and errors
Error codes + out params	`std::expected<T, E>`	Composable, type-safe errors
`union`	`std::variant`	Type-safe, no silent UB
Raw `mutex.lock()/unlock()`	`std::scoped_lock`	Exception-safe, no deadlocks
`std::thread`	`std::jthread`	Auto-join, stop token support
`assert()` macro	`contract_assert` (C++26)	Visible to tooling, configurable
Manual CRTP	Deducing `this` (C++23)	Simpler, no template boilerplate
Macro code generation	Reflection (C++26)	Zero-overhead, composable

See anti-patterns.md for the full table (30+ patterns).

Decision Tree

What are you doing?|+-- Writing new C++ code?|   +-- Use modern idioms by default (C++20/23)|   +-- Choose the newest standard your compiler supports|   +-- See Feature Tiers below|+-- Modernizing existing code?|   +-- Start with Tier 1 (C++20/23) replacements|   +-- Prioritize by security impact (memory > types > style)|   +-- See anti-patterns.md for the migration table|+-- Security-critical code?|   +-- Enable compiler hardening flags (see below)|   +-- Enable hardened libc++ mode|   +-- Run sanitizers in CI|   +-- See safe-idioms.md and compiler-hardening.md|+-- Using C++26 features?    +-- Reflection: YES, plan for it (GCC 16+)    +-- Contracts: cautiously, for new API boundaries    +-- std::execution: wait for ecosystem maturity    +-- See cpp26-features.md

What are you doing?|+-- Writing new C++ code?|   +-- Use modern idioms by default (C++20/23)|   +-- Choose the newest standard your compiler supports|   +-- See Feature Tiers below|+-- Modernizing existing code?|   +-- Start with Tier 1 (C++20/23) replacements|   +-- Prioritize by security impact (memory > types > style)|   +-- See anti-patterns.md for the migration table|+-- Security-critical code?|   +-- Enable compiler hardening flags (see below)|   +-- Enable hardened libc++ mode|   +-- Run sanitizers in CI|   +-- See safe-idioms.md and compiler-hardening.md|+-- Using C++26 features?    +-- Reflection: YES, plan for it (GCC 16+)    +-- Contracts: cautiously, for new API boundaries    +-- std::execution: wait for ecosystem maturity    +-- See cpp26-features.md

Feature Tiers

Features are ranked by practical usability today, not by standard version.

Tier 1: Use Today (C++20/23, solid compiler support)

Feature	Replaces	Standard
Concepts + `requires`	SFINAE, `enable_if`	C++20
Ranges + views	Raw iterator loops	C++20
`std::span<T>`	Pointer + length	C++20
`std::format`	`sprintf`, iostream chains	C++20
Three-way comparison `<=>`	Manual comparison operators	C++20
`std::jthread`	`std::thread` + manual join	C++20
Designated initializers	Positional struct init	C++20
`std::expected<T,E>`	Error codes, exceptions at boundaries	C++23
`std::print` / `std::println`	`printf`, `std::cout <<`	C++23
Deducing `this`	CRTP, const/non-const duplication	C++23
`std::flat_map`	`std::map` for read-heavy use	C++23
Monadic `std::optional`	Nested if-checks on optionals	C++23

See cpp20-features.md and cpp23-features.md.

Tier 2: Deploy Now (no standard bump needed)

These improve safety without changing your C++ standard version:

Compiler hardening flags — -D_FORTIFY_SOURCE=3, -fstack-protector-strong, -ftrivial-auto-var-init=zero
Hardened libc++ — -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_FAST for ~0.3% overhead bounds-checking
Sanitizers in CI — ASan + UBSan as minimum; TSan for concurrent code
Warning flags — -Wall -Wextra -Wpedantic -Werror

See compiler-hardening.md.

Tier 3: Plan For (C++26, worth restructuring around)

Reflection is the single most transformative C++26 feature. It eliminates:

Serialization boilerplate (one generic function replaces per-struct to_json)
Code generators (protobuf codegen, Qt MOC)
Macro-based registration and enum-to-string hacks

GCC 16 (April 2026) has reflection merged. Plan new code to benefit from it.

Tier 4: Watch (C++26, needs maturation)

Contracts (pre/post/contract_assert) — Better than assert(), but no virtual function support and limited compiler support. Adopt cautiously for new API boundaries.
std::execution (senders/receivers) — Powerful async framework, but steep learning curve, no scheduler ships with it, and poor documentation. Wait for ecosystem maturity.

See cpp26-features.md.

Compiler Hardening Quick Reference

Essential Flags (GCC + Clang)

-Wall -Wextra -Wpedantic -Werror-D_FORTIFY_SOURCE=3-fstack-protector-strong-fstack-clash-protection-ftrivial-auto-var-init=zero-fPIE -pie-Wl,-z,relro,-z,now

-Wall -Wextra -Wpedantic -Werror-D_FORTIFY_SOURCE=3-fstack-protector-strong-fstack-clash-protection-ftrivial-auto-var-init=zero-fPIE -pie-Wl,-z,relro,-z,now

Clang-Specific

Hardened libc++ (Clang/libc++ only)

Google deployed this across Chrome and their server fleet: ~0.3% overhead, 1000+ bugs found, 30% reduction in production segfaults.

See compiler-hardening.md for the full guide.

Rationalizations to Reject

Rationalization	Why It's Wrong
"It compiles without warnings"	Warnings depend on which flags you enable. Add `-Wall -Wextra -Wpedantic`.
"ASan is too slow for production"	Use GWP-ASan for sampling-based production detection (~0% overhead).
"We only use safe containers"	Iterator invalidation and unchecked `optional` access are still exploitable.
"Smart pointers are slower"	`std::unique_ptr` has zero overhead vs raw pointers. Measure before claiming.
"Our code doesn't have memory bugs"	Google found 1000+ bugs when enabling hardened libc++. So did everyone else.
"C++26 features aren't available yet"	C++20/23 features are. Hardening flags work on any standard. Start there.
"Modern C++ is harder to read"	`std::expected` is more readable than checking error codes across 5 out-params.

Best Practices Checklist

Source and attribution

Source:trailofbits/skillsinplugins/modern-cpp/skills/modern-cppat commit82fe822

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Modern Cpp

Modern C++

When to Use This Skill

When NOT to Use This Skill

Anti-Patterns to Avoid

Decision Tree

Feature Tiers

Tier 1: Use Today (C++20/23, solid compiler support)

Tier 2: Deploy Now (no standard bump needed)

Tier 3: Plan For (C++26, worth restructuring around)

Tier 4: Watch (C++26, needs maturation)

Compiler Hardening Quick Reference

Essential Flags (GCC + Clang)

Clang-Specific

Hardened libc++ (Clang/libc++ only)

Rationalizations to Reject

Best Practices Checklist

Read Next

Source and attribution

More from trailofbits/skills

Vector Forge

Wycheproof

Ruzzy

Ossfuzz

Libfuzzer

Trailmark

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices