Did you mean C11 there or C++11? I'm not sure why C11 is relevant in a discussion about C++. MSVC's support of C has been abysmal for ages, but this has no reflection on its C++ support. Of which it definitely supports all of C++11. And 14. And 17. And even complete support for C++20
For C++20, GCC is "only" missing module support, but otherwise supports everything else. Clang is lagging behind, though.
I mean C11 because it's an example of a major release in a major language that became unusable in practice because a compiler vendor decided it wasn't important to support it in full. Now you can't bump your compiler version to C11 if you want stable portability. This is relevant because it's what happens to C++ if it demands too much from compiler developers.
>For C++20, GCC is "only" missing module support, but otherwise supports everything else. Clang is lagging behind, though.
Then I'll rephrase: it's not only not available widely, it's not available at all.
C isn't a major language on windows, at least according to Microsoft, whereas c++ is. It'd be like complaining about the state of Java on iOS. C11 doesn't demand much of anything from the compiler. It's definitely not from overbearing demands made by the language.
Did you mean C11 there or C++11? I'm not sure why C11 is relevant in a discussion about C++. MSVC's support of C has been abysmal for ages, but this has no reflection on its C++ support. Of which it definitely supports all of C++11. And 14. And 17. And even complete support for C++20
For C++20, GCC is "only" missing module support, but otherwise supports everything else. Clang is lagging behind, though.
https://en.cppreference.com/w/cpp/compiler_support