Since when can you use it?The standard and the first GCC, Clang and MSVC releases for each C++ feature

It’s free, with nothing to sign up for or install. Search it, filter it and link to it as often as you like. Cpp Next earns from its articles, not from the tool, and there are no ads inside the tables.

From each vendor’s own pages: GCC’s C++ standards support page and the libstdc++ status tables in the GCC manual, plus GCC’s release notes for the C++23 and C++26 library features those tables don’t list; Clang’s C++ status page, libc++’s status pages and LLVM’s archived libc++ documentation; Microsoft’s C/C++ language conformance table, the Microsoft STL changelog it points to and, for the C++11 library, Microsoft’s C++11 feature page. Each standard’s Sources line links the pages its cells came from. Cpp Next isn’t affiliated with the C++ committee or with any of these vendors.

The first release the vendor lists with full support for the paper that added the feature. In the GCC column a language cell is a GCC release (7) and a library cell is a libstdc++ release (7.1, the first release of GCC 7). In the Clang column a library cell is the LLVM release whose libc++ ships the feature. MSVC cells are Visual Studio versions; Visual Studio 2026 18.0 and 18.6 shipped MSVC Build Tools 14.50 and 14.51. (partial) means the vendor marks its support incomplete; Not yet means the vendor’s status page or tracking issue lists the feature as unimplemented; and Yes, Partial or Complete with no number is the vendor’s own status word, used where its page gives a status instead of a release.

Because Microsoft dates C++11 in two groups. Its conformance table gives Visual Studio 2015 for the core language features, apart from a few it names separately: two-phase name lookup and expression SFINAE came in Visual Studio 2017 15.7. Its C++11 feature page, in the Visual Studio 2015 documentation, says Visual Studio 2012 implemented the C++11 Standard Library, simulating variadic templates where the compiler lacked them; real variadic templates came in Visual Studio 2013. MSVC in Visual Studio 2017 and later has no mode older than /std:c++14, its default.

Because that is what the vendor’s page gives. libstdc++’s manual marks each part of the C++11 and C++14 library as implemented (Y, written Yes here) or Partial without saying from which release; it lists std::thread as Partial because thread::id comparisons aren’t well-defined, and std::function for missing allocator support. libc++’s documentation calls its C++11 support complete without per-feature releases, while its archived C++14 status page does give them. Clang’s C++20 page lists coroutines as Partial with no release number, because of open stability and ABI issues on Windows. A status word says the vendor ships the feature, or part of it, today; it doesn’t say since when.

Because libc++’s own status page as it stood at LLVM 4.0 (the llvmorg-4.0.0 tag) marks complete in 4.0 the papers that change these types (P0307R2 and P0032R3 for std::optional, P0032R3 for std::any, P0254R2 for std::string_view), and a paper that changes a type can’t be complete in a release that lacks it; the cell is read that way rather than stated outright. The paper that added all three, Library Fundamentals V1 (P0220R1), is marked complete only in LLVM 16, when its last piece landed, so 16 would be the wrong answer.

Waiting for Microsoft. Its conformance table has no C++26 language rows yet, so no MSVC cell can be filled, and the C++26 table holds only library features all three vendors report on. For now, GCC’s page lists reflection in GCC 16 behind -freflection, contracts in GCC 16 and pack indexing in GCC 15; Clang’s lists pack indexing in Clang 19 and reflection and contracts as not implemented. std::execution waits for GCC: neither libstdc++’s manual nor GCC’s release notes list it yet.

None of the pages these tables come from says so yet. GCC’s status page says the next revision of the standard is expected to be published in 2026 and calls GCC’s support experimental, Clang calls its mode C++2c, and libc++ notes that features in unreleased drafts of the standard are subject to change. Treat the C++26 rows as early support that can still move.

Usually one of four things. The flag: a C++23 feature needs -std=c++23, or /std:c++latest on MSVC, and some need more, such as -fmodules for modules in GCC, or -fcoroutines for coroutines in GCC 10. The library: the GCC column is libstdc++ and the Clang column is libc++, so Clang building against libstdc++ follows the GCC column for library features. A cell marked (partial). Or Apple’s Clang in Xcode, which has its own version numbers and isn’t covered here. If it’s none of these, send the feature, the compiler version and the flags through the contact page.

Each standard’s Checked line gives the day its cells were last read against the vendors’ pages. They’re read again after each GCC, LLVM and Visual Studio release, and the date moves with each check.

Through the contact page: the feature, the cell, and the vendor page that says otherwise. A row goes in when every one of its cells can be shown from a vendor’s page, so that link is what gets it in.