Move Slow and Break Things
Alisdair Meredith
The C++ Standard has adopted a process to advertise that we would like to remove or change a feature in some future Standard, allowing developers to adapt to such revised rules and to update their code at a time of their choosing, rather than as a cost of updating to the latest Standard. We call this process deprecation.
Eventually, the time comes to remove those deprecated features, even at the cost of sacrificing compatibility with code that has not taken the chance to update. Since backward compatibility is important, we move slowly, over a period of years and multiple Standards, but eventually we will break things.
This session will inform the audience of all the ways their code might break or change meaning when upgrading their code to C++26 and of some remaining deprecated features that could be a consideration for the anticipated C++29.