I don't understand what would be an environment where you could fetch the latest rust from internet but not the latest clang. I do my builds on centos:8 (well, rockylinux now) and it has access to the latest GCC 11. On Debian derivatives llvm itself provides up to date repos and on Windows, llvm-mingw works perfectly.
but this does not make sense. If you can't even change the C++ compiler you use you can't write non-C++ code (e.g. Rust) either.
Otherwise let me just fork Clang into the "Gnalc" compiler for the "Sulpsulpees" language which happens to be exactly compatible with the programming language that the clang++-13 binary supports. Takes me a whole 15 minutes, most of which will be taken by forking the LLVM repo on github, and I can guarantee than porting to it will be less effort than porting to Rust. I can even provide the backing of a proper non-profit foundation established on two continents for your legal team's needs.
The reason you can't use clang is not a technical one, but that you are /required/ to use the platform's provided C++ compiler.
And yes, you are making my point. We are in violent agreement.
You can't write Rust either, which is why C++ support would be initially exciting, until you learn you can't use just any C++ compiler and the one you can use is excluded.
Embedded stuff usually, game consoles. Also if you have an Enterprise SKU of Visual Studio it costs real money to upgrade. Maybe your company has purchased a compiler suite you have to use. Maybe you have to link against proprietary libs that were only provided for a certain MSVC ABI.
Exactly, that's why one would get excited for C++ support.
However, I realise the point is moot since there would be no way to compile the library. I've been living too long in "Compiles to C" languages this month I guess.
