State of C++ 2026
2025 brought major changes to C++. C++26 achieved feature-complete status in June, delivering static reflection, what Herb Sutter called "more transformational than any 10 other major features combined", alongside contracts and the std::execution async framework. Meanwhile, WG21 rejected the Safe C++ proposal in favor of Profiles, sparking fierce community debate. CISA and FBI recommended publishing memory safety roadmaps by end of 2025 (non-binding guidance), and a Microsoft distinguished engineer outlined an ambitious _goal_ (later clarified as research, not a company-wide commitment) to remove C/C++ by 2030 (The Register, TechRadar). Visual Studio 2026 shipped with deep GitHub Copilot integration, GCC 15 bumped the default to C23, and CMake 4.0 marked 25 years of build system evolution.

Actions for 2026: Audit codebases for C++26 readiness, particularly reflection and contracts. Review the Profiles whitepaper when published. Publish or update memory safety roadmaps and execute against them. Test CLion Nova and VS 2026 AI features. Migrate Qt 5 projects to Qt 6.10 LTS.
January 2025
vcpkg Surpasses 2,524 Libraries
February 2025
Bjarne Stroustrup's "Call to Action"
WG21 Hagenberg Meeting
C++Online 2025
March 2025
MISRA C:2025 Published
C++ Dynamic Debugging at GDC
CMake 4.0.0
CMAKE_POLICY_VERSION_MINIMUM, deprecated pre-3.5 compatibility, added CMAKE_LINK_WARNING_AS_ERROR, and improved C++20 modules support.April 2025
ACCU Conference
Qt 6.9
GitHub Copilot C/C++ Support
GCC 15.1
= delete("reason") (P2573R2), variadic friends (P2893R3), and constexpr placement new (P2747R2).Activision 50% Build Time Reduction
C++Now 2025
Pure Virtual C++ 2025
May 2025
Visual Studio 2022 17.14
JetBrains Developer Ecosystem Survey
Qt 5.15 Standard Support Ends
June 2025
C++26 Feature Complete
[[pre:]]/[[post:]]/contract_assert, std::execution sender/receiver framework, SIMD types from Parallelism TS 2, parallel algorithms for Ranges, and std::embed.C++ on Sea 2025
CISA/NSA Memory Safety Guidance
Chrome V8 Zero-Day
July 2025
C++26 CD Ballot
Meta's C-to-Rust Migration
CppNorth 2025
vcpkg license-report Command
August 2025
Dependabot vcpkg Support
NASA Software Testing Deep-Dive
LLVM 21.1
September 2025
CppCon 2025
VS Insiders C++ Copilot Preview
Safe C++ Proposal Abandoned
Embedded C++ World 2025
October 2025
Qt SVG Critical Vulnerabilities
Qt 6.10 LTS
vcpkg 2,691 Ports
C++ Day Italy
GitHub Copilot Build Analysis
November 2025
WG21 Kona Meeting
OWASP Top 10 Supply Chain
Chrome V8 Type-Confusion Zero-Day
Meeting C++ 2025
Visual Studio 2026 GA
GCC C++20 Default Proposal
December 2025
Red Hat Qt 3D Security Advisory
CLion 2025.3
Microsoft C/C++ Elimination Goal
GCC AI Patch Debate
cpp-httplib Header Spoofing
GitHub Copilot C++ Public Preview
Kernel Rust Experiment Update
GitHub Octoverse 2025
C++ 2026 Watchlist

1. C++26 Final Approval
When: March 23-28, 2026 (London WG21 meeting); late 2026 formal publication
Context: Feature-complete C++26 includes static reflection, contracts, std::execution, SIMD types, and parallel Ranges. The London meeting will finish technical approval after national body comment resolution.
Action: Track isocpp.org for final wording; begin planning adoption of reflection for serialization and RPC; review contracts for production use.
2. Memory Safety Roadmaps
When: End of 2025 (publish); 2026 execution/follow-through
Context: CISA and NSA urged adoption of memory-safe languages, while "Product Security Bad Practices" recommends publishing memory safety roadmaps by the end of 2025. Microsoft has a research-stated goal (not a company-wide commitment) to remove C/C++ by 2030. In large codebases, memory safety issues can represent ~70% of reported vulnerabilities (e.g., Microsoft historically).
Action: Publish internal memory safety roadmaps; review hardened containers and static analysis; document use of bounds-checking, sanitizers, and safe coding guidelines.
3. Profiles Whitepaper
When: Expected 2026 publication; implementation timeline unclear
Context: The committee rejected Safe C++ borrow-checker in favor of Profiles (P3038/P3081). The committee appointed Whitepaper editors at the November Kona meeting. Critics argue Profiles lack implementation and cannot enforce strict safety without aliasing/lifetime annotations.
Action: Track whitepaper progress; review whether Profiles meet organizational security requirements; consider alternative safety strategies (Rust interop, static analysis).
4. GCC 16 and LLVM 22
When: GCC 16 expected April 2026; LLVM 22 February 2026
Context: GCC 16 adds an Algol 68 front-end and Intel AVX10 support; a proposal to make C++20 the default dialect is under discussion (gcc-patches). LLVM continues rapid C++26 feature adoption and hardware enablement.
Action: Test codebases with GCC trunk/LLVM main; update CI for C++20 default; review AVX10 for SIMD-heavy workloads.
5. AI Tooling Maturation
When: Throughout 2026
Context: GitHub Copilot C++ integration reached public preview with symbol-aware editing. CLion Nova delivers 4x performance. VS 2026 ships Profiler and Debugger Agents. GCC community opposed fully LLM-written patches.
Action: Review VS 2026 and CLion 2025.3 AI features; establish policies for AI-assisted code review; document AI contribution guidelines for open-source projects.
6. CppCon 2026 and C++26 Celebration
When: September 12-18, 2026 (Aurora, CO)
Context: CppCon 2026 will celebrate the finalized C++26 standard. Guy Davidson's first year as WG21 convenor. C++Now 2026 (May 4-8) features "Beyond C++" tracks on Rust interoperability.
Action: Submit conference proposals; plan C++26 adoption presentations; engage with post-C++26 proposals (pattern matching, trivial relocatability).
7. Package Manager Evolution
When: Throughout 2026
Context: vcpkg reached 2,691 ports (Oct 2025 update) with Dependabot support. Conan launched MCP Server for AI agent integration. C++ Package Manager (CppPM) standardization effort ongoing.
Action: Review Conan Audit for vulnerability scanning; add Dependabot for vcpkg manifests; track CppPM standardization progress.
8. Qt 6 Migration Completion
When: Urgent. Qt 5.15 standard support ended May 26, 2025
Context: Qt 5.15 standard support ended May 26, 2025. Qt 6.10 LTS shipped with Android 15/16 and 16K page support. Critical SVG vulnerabilities (CVE-2025-10728/10729) required immediate patching.
Action: Complete Qt 5 to Qt 6 migrations; update to Qt 6.8.5+/6.9.3+/6.10.1+ for security patches; review commercial vs. open-source licensing implications.







