Things C++ 20 Deliberately Broke

[norm]

On Sunday, 25 September 2022 at 23:01:52 UTC, Walter Bright wrote:
> https://docs.google.com/presentation/d/1HwLNSyHxy203eptO9cbTmr7CH23sBGtTrfOmJf9n0ug/edit?usp=sharing&resourcekey=0-GH5F3wdP7D4dmxvLdBaMvw
>
> https://news.ycombinator.com/item?id=32969957

I agree with the general sentiment on ycombinator, most of the 
"breakages" are things deprecated because it plugs a hole in the 
language. So a Chromium developer is on the migration trail and 
doesn't like it. Many of the "solutions" are things like "use 
explicit casts", which is a good thing because it exposes where 
they are side-stepping the type system to reopen the holes 
plugged by C++20.

There are two paths; Python2/3 new language or or deprecation 
like C++ and D. Either way end-users have to walk that migration 
at some point to upgrade to the new language.