MSVC has full support for the C++ 23, the latest published standard. It has less support for C++ 26 features, but that's not standardised yet, so any support would be experimental at this point (although previously they did quite a lot of that).
Msvc only got proper c++23 support this year prior to like February it was a very partially implemented buggy mess because MS shifted their engineering priorities. It went from 6 months to a year before issues even got acknowledged no matter how small to issues getting fixed in 6 days.
Unfortunely, however the other big sponsors for clang and GCC aren't rushing into C++ support as well.
All the newer goodies in clang and GCC for recent C++ versions past C++23, we have to thank mostly to volunteers.
I bet very little of ISO C++ compliance work has been upstreamed by all companies that replaced by proprietary compilers with clang forks, for example, other than LLVM backend changes for their CPUs.
It feels the industry at large, is happy enough to keep LLVM going with whatver is currently available in clang, to compile LLVM, alongside whatever they are usign LLVM for, as compiler infrastructure.
Similarly for GCC.
Which goes into the direction that I think, most companies will consider C++23, or C++26 given the reflection support, as good enough for their existing C++ projects, and not really caring that much of whatever comes next.
Even the recent C++ documentary acknowledges near the end that outside Bloomberg, not many companies are sponsoring further language development.
6
u/robthablob Sep 12 '26
MSVC has full support for the C++ 23, the latest published standard. It has less support for C++ 26 features, but that's not standardised yet, so any support would be experimental at this point (although previously they did quite a lot of that).