Modern Cpp
Trail of BitsOfficialPublished by Trail of Bits
- Skill
- Guidelines
- Software development
- CC-BY-SA-4.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a comprehensive framework for transitioning C++ codebases toward modern standards. It emphasizes patterns that eliminate common vulnerability classes, such as memory leaks and buffer overflows, by replacing legacy C-style constructs with modern, type-safe alternatives. The content includes migration tables for anti-patterns, compiler hardening configurations, and feature tiers based on practical usability.
What it does
- Provides migration paths from legacy C++ patterns to modern C++20/23/26 idioms.
- Lists specific anti-patterns and their safer, modern replacements.
- Details compiler hardening flags for GCC and Clang to improve security.
- Explains the use of hardened libc++ modes for bounds-checking.
- Categorizes C++ features by their current practical deployment readiness.
- Offers a checklist for adopting safe coding practices in new and existing projects.
When to use it
- When writing new C++ functions, classes, or libraries.
- When modernizing legacy C++ codebases to improve safety and maintainability.
- When working on security-critical or safety-sensitive C++ applications.
- When reviewing C++ code to ensure adoption of modern idioms.
- When configuring compiler and linker settings for enhanced security.
Advantages
- Reduces vulnerability classes like memory leaks and buffer overflows.
- Improves code readability and reduces boilerplate through modern language features.
- Provides actionable, security-focused compiler and linker configurations.
- Offers clear, evidence-based guidance on replacing legacy C-style constructs.
- Helps align code with current C++ standards for better long-term maintainability.
Usage examples
- “How should I replace raw pointers in my C++ code?”
- The skill recommends using std::unique_ptr for exclusive ownership or std::shared_ptr for shared ownership to ensure RAII semantics and eliminate manual memory management.
- “What are the recommended compiler flags for hardening a C++ project?”
- The skill provides a list of essential flags including -D_FORTIFY_SOURCE=3, -fstack-protector-strong, and -ftrivial-auto-var-init=zero, along with linker settings like -Wl,-z,relro,-z,now.
- “How can I replace printf in C++23?”
- The skill suggests using std::print or std::println, which are type-safe and avoid the format string vulnerabilities associated with printf.
- “What is the modern alternative to SFINAE?”
- The skill advises using C++20 Concepts and the requires clause to constrain templates, which provides more readable code and clearer error messages.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/trailofbits/modern-cpp/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip modern-cpp.zip -d .agents/skills
Documentation by Trail of Bits
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.mdFeature 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=zeroHardened libc++ —
-D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_FASTfor ~0.3% overhead bounds-checkingSanitizers in CI — ASan + UBSan as minimum; TSan for concurrent code
Warning flags —
-Wall -Wextra -Wpedantic -Werror
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 thanassert(), 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,nowClang-Specific
-Wunsafe-buffer-usageHardened libc++ (Clang/libc++ only)
-D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_FASTGoogle 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
[ ] Use smart pointers for ownership, raw pointers only for non-owning observation
[ ] Prefer
std::spanover pointer + length for function parameters[ ] Use
std::expectedfor functions that can fail with typed errors[ ] Constrain templates with concepts, not SFINAE
[ ] Enable compiler hardening flags and hardened libc++ in all builds
[ ] Run ASan + UBSan in CI; add TSan for concurrent code
[ ] Use
constexpr/constevalwhere possible (UB-free by design)[ ] Mark functions
[[nodiscard]]when ignoring the return value is likely a bug[ ] Prefer value semantics; use
std::variantoverunion,enum classoverenum[ ] Initialize all variables at declaration
Read Next
anti-patterns.md — Full legacy-to-modern migration table (30+ patterns)
cpp20-features.md — Concepts, ranges, span, format, coroutines
cpp23-features.md — expected, print, deducing this, flat_map
cpp26-features.md — Reflection, contracts, memory safety improvements
compiler-hardening.md — Flags, sanitizers, hardened libc++
safe-idioms.md — Security patterns by vulnerability class
Files
- ATTRIBUTION.mdAdded by AutoGineer924 B
- LICENSELicence file added by AutoGineer19.7 KiB
- SKILL.md8.5 KiB
- references/anti-patterns.md5.5 KiB
- references/compiler-hardening.md7.3 KiB
- references/cpp20-features.md7.0 KiB
- references/cpp23-features.md7.0 KiB
- references/cpp26-features.md7.5 KiB
- references/safe-idioms.md8.1 KiB
references/cpp23-features.md
C++23 Features (Usable Today)
These features have solid compiler support (GCC 13+, Clang 17+, MSVC 17.4+) and deliver immediate value. Adopt them now.
std::expected<T, E>
Type-safe error handling with monadic chaining. The most impactful C++23 feature for everyday code.
What It Replaces
Error codes + output parameters, nullable returns, exceptions at API boundaries where failure is expected (not exceptional).
Basic Usage
#include <expected>
enum class ParseError { empty_input, invalid_format, overflow };
std::expected<int, ParseError> parse_int(std::string_view s) {
if (s.empty())
return std::unexpected(ParseError::empty_input);
// ... parsing logic ...
return 42;
}
// Caller must handle both paths
auto result = parse_int("123");
if (result) {
use(*result); // or result.value()
} else {
handle(result.error());
}Monadic Chaining
Chain operations without nested if-checks:
std::expected<Config, Error> load_config(const Path& p) {
return read_file(p) // expected<string, Error>
.and_then(parse_toml) // expected<TomlValue, Error>
.and_then(validate_config) // expected<Config, Error>
.transform(apply_defaults); // expected<Config, Error>
}.and_then(f)— if value, callf(value)which returns a newexpected.transform(f)— if value, callf(value)and wrap result inexpected.or_else(f)— if error, callf(error)which returns a newexpected.transform_error(f)— if error, callf(error)and wrap result
When to Use vs Exceptions
Use
std::expected: expected failures (file not found, parse error, validation failure), performance-critical paths, codebases that ban exceptionsUse exceptions: truly exceptional conditions (out of memory, programmer error), deep call stacks where propagation cost matters
Compiler Support
GCC 13+, Clang 17+, MSVC 17.4+
std::print / std::println
Type-safe formatted output. Essentially fmt::print standardized.
Basic Usage
#include <print>
std::println("Hello, {}!", name); // with newline
std::print("x = {}, y = {}\n", x, y); // without auto-newline
std::println("{:>10.2f}", 3.14159); // format spec: right-aligned, 2 decimal
std::println("{0} is {0}", value); // reuse argument by indexWhat It Replaces
// BEFORE: printf (type-unsafe, format string vulnerabilities)
printf("Name: %s, Age: %d\n", name.c_str(), age);
// BEFORE: iostream (verbose, stateful, slow)
std::cout << "Name: " << name << ", Age: " << age << std::endl;
// AFTER: type-safe, readable, fast
std::println("Name: {}, Age: {}", name, age);Relationship to {fmt}
std::print IS the {fmt} library adopted into the standard, by the same author (Victor Zverovich). If you already use {fmt}, switching to std::print removes one dependency. {fmt} still has extras std::print lacks (color output, named arguments).
Compiler Support
GCC 14+, Clang 18+, MSVC 17.4+
Deducing this
Eliminates const/non-const overload duplication and simplifies CRTP.
The Problem It Solves
// BEFORE: duplicated logic for const and non-const
class Buffer {
std::vector<char> data_;
public:
char& operator[](size_t i) { return data_[i]; }
const char& operator[](size_t i) const { return data_[i]; }
// Often 4 overloads: const/non-const x lvalue/rvalue
};
// AFTER: one function handles all qualifications
class Buffer {
std::vector<char> data_;
public:
template <typename Self>
auto&& operator[](this Self&& self, size_t i) {
// forward_like, not forward: vector::operator[] is not ref-qualified,
// so forwarding the object alone would drop the rvalue case
return std::forward_like<Self>(self.data_[i]);
}
};Simplified CRTP
// BEFORE: arcane template pattern
template <typename Derived>
struct Base {
void interface() {
static_cast<Derived*>(this)->implementation();
}
};
// AFTER: no template parameter needed
struct Base {
void interface(this auto&& self) {
self.implementation();
}
};Recursive Lambdas
// BEFORE: std::function or Y-combinator
std::function<int(int)> fib = [&](int n) {
return n <= 1 ? n : fib(n-1) + fib(n-2);
};
// AFTER: direct recursion
auto fib = [](this auto&& self, int n) -> int {
return n <= 1 ? n : self(n-1) + self(n-2);
};Compiler Support
GCC 14+, Clang 18+, MSVC 19.32+
std::ranges::to (Materializing Views)
Converts lazy range views into concrete containers. The missing piece from C++20 ranges.
#include <ranges>
auto vec = data
| std::views::filter(is_valid)
| std::views::transform(process)
| std::ranges::to<std::vector>(); // materialize into a vector
// Works with any container
auto set = data
| std::views::transform(normalize)
| std::ranges::to<std::set>();Without std::ranges::to, you had to manually construct containers from view iterators — awkward and error-prone. This completes the C++20 ranges story.
Compiler Support
GCC 14+, Clang 17+, MSVC 17.4+
std::flat_map / std::flat_set
Cache-friendly sorted containers backed by contiguous storage.
When to Prefer Over std::map
Read-heavy workloads — lookup is 8-17x faster than
std::mapfor small-medium sizesSmall-to-medium maps (up to ~1000 elements)
Cache-sensitive code — contiguous memory vs node-based tree
When NOT to Use
Insert-heavy workloads — insertion is O(n) due to shifting elements
Large maps with frequent mutations —
std::map's O(log n) insert winsIterator stability required — flat containers invalidate iterators on insert
Usage
#include <flat_map>
std::flat_map<std::string, int> scores;
scores["alice"] = 100;
scores["bob"] = 85;
auto it = scores.find("alice"); // fast binary search on sorted vectorCompiler Support
GCC 15+, Clang 18+, MSVC 17.6+
std::generator<T>
Lazy coroutine generators for producing sequences on demand.
Usage
#include <generator>
std::generator<int> fibonacci() {
int a = 0, b = 1;
while (true) {
co_yield a;
auto next = a + b;
a = b;
b = next;
}
}
// Lazy — only computes as many values as consumed
for (auto val : fibonacci() | std::views::take(10)) {
std::println("{}", val);
}Compiler Support
MSVC 17.4+, GCC 14+ (partial), Clang catching up. Wait for broader support before relying on it.
import std
Import the entire standard library as a module.
import std; // replaces ALL #include <...> for standard headers
int main() {
std::println("Hello from modules!");
}Caveats
Build system support varies (CMake 3.28+ with some generators)
Third-party libraries are mostly not module-ready
Mixing headers and modules requires care
Best for new projects; migration of existing code is nontrivial
Compiler Support
GCC 15+, Clang 18+ (partial), MSVC 17.5+
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Trail of Bits
- Publisher
- Trail of Bits (Official)
- Source
- trailofbits/skills · plugins/modern-cpp/skills/modern-cpp · commit e4dd0bb
- Licence
- Creative Commons Attribution-ShareAlike 4.0 International (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Trail of Bits.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download modern-cpp.zip