Things C++ 20 Deliberately Broke

[Siarhei Siamashka]

On Monday, 26 September 2022 at 03:24:57 UTC, norm wrote:
> There are two paths; Python2/3 new language

https://www.techrepublic.com/article/programming-languages-why-python-4-0-will-probably-never-arrive-according-to-its-creator/

Python developers discovered that people dislike compatibility 
breaking
changes. So if a programming language wants to be successful, then
this has to be taken into account.

> or deprecation like C++ and D.

C++ and D are actually radically different. Older versions of the 
C++
standard are still supported via the '-std=c++98' or '-std=c++17' 
option
in GCC (or its equivalent in the other C++ compilers). And C++ is 
not
unique. For example, Rust also supports different language 
editions.
If Python developers decided to keep both Python2 and Python3
maintained forever, then it would be similar to C++ and Rust.

D doesn't offer anything like this right now.

> Either way end-users have to walk that migration at some point 
> to
> upgrade to the new language.

End-users don't have to migrate if they still have an option to 
keep
using the older version of the language standard when compiling 
their
code. This is very useful for large projects. Chromium developers
are safely staying at C++17 while evaluating C++20. Nobody is 
pulling
the rug from under their feet.