// toolset / matrix
C++26 compiler support
Per-feature, per-compiler support for C++26 reflection and adjacent papers. Cells in the per-example groups link to runnable Compiler Explorer URLs we re-verify on every publish.
Reading the matrix. The first table is paper-level feature status across compilers we test. The remaining tables are per-post: each row is one example file from a wro.cpp post, each cell is a runnable Compiler Explorer link under that compiler. Green cells compile and run cleanly today; greyed-out cells were not attempted yet under that compiler.
Compilers we track.clang-p2996 = the Bloomberg fork (the C++26 reflection reference implementation), invoked with-std=c++26 -freflection-latest -stdlib=libc++.GCC 16.1 = mainline GCC 16.1 (released April 2026), invoked with -std=c++26 -freflection. MSVC and EDG are listed in the paper-level table for reference but we do not yet run examples against them.
Methodology
Per-example cells are auto-derived fromscripts/shorten-examples.py runs against the godbolt API. Each successful site build reflects the latest verified state; the "last regenerated" date in the badge above is the modification time of src/data/godbolt-permalinks.yml.
Paper-level cells in the top table are hand-curated fromsrc/data/compatibility-features.yml and refreshed quarterly (or on major compiler releases). When a new ISO C++ paper ships across compilers, it lands here first, then radiates into the per-example tables once a wro.cpp post covers it.
See also: how we test, in general.