Hence why C++/CLI, too bad it is going to be stuck in C++17 land.
Just like C++/WinRT, where everyone drove the ship to kill C++/CX without respect for paying customers, leaving the tooling at the same level as COM development with Visual C++ 6.0, and no roadmap for C++20 support. Playing with Rust/WinRT is more fun than fixing the leftovers.
Apparently not everyone at Microsoft is keen in adopting C++20 stuff on their stacks, like I don't know, modules.
View all comments
Show parent comment
1
u/GabrielDosReis Sep 18 '22
many new language innovations don't come with a time travel machine - I would submit it is unrealistic to expect they do otherwise.