From what I understand, when the schedule started to slip, the team made a decision to not do a death march just so it happened two months ago instead of today. This seems healthy to me.
On the other hand, people will be able to use Rust 2024 in production in a few month, if not now. While most C++ codebase are still stuck with C++17 or older.
Just like many C code bases are stuck on C89, many Python in Python 2, Java in Java 8, .NET in .NET Framework,...
Not that every compiler is up to date, but at very least clang, gcc and vc++ have already quite good coverage of C++20, and clang/vc++ modules mostly work, good enough that I only use modules in my hobby projects.
It starts by projects, companies, actually wanting to adopt new toolchains.
From what I understand, when the schedule started to slip, the team made a decision to not do a death march just so it happened two months ago instead of today. This seems healthy to me.
On the other hand, people will be able to use Rust 2024 in production in a few month, if not now. While most C++ codebase are still stuck with C++17 or older.
Just like many C code bases are stuck on C89, many Python in Python 2, Java in Java 8, .NET in .NET Framework,...
Not that every compiler is up to date, but at very least clang, gcc and vc++ have already quite good coverage of C++20, and clang/vc++ modules mostly work, good enough that I only use modules in my hobby projects.
It starts by projects, companies, actually wanting to adopt new toolchains.
The code was frozen already in 2024, it just took some time to actually release it.
Same with C23 and C++23, things take time to iron out.