Recent concerns regarding C++ memory safety have sparked interest in projects like TrapC and Safe C++. Bjarne Stroustrup, the designer of C++, advocates for the implementation of profiles to enhance safety measures in the language. He argues that profiles can help impose regulations on features and maintain type and resource safety. Stroustrup warns against the risks of not adopting these changes and suggests integrating support for initial profiles in C++ 26, thereby continuing C++'s evolution without breaking existing code or features.
The sky isn't falling, but unless we act now and get C++ onto a track supporting a flexible framework of profiles, we risk a painful decline.
Profiles can offer guarantees for imposing restrictions on existing features. C++ type safety and resource safety, including memory safety, were aims of C++ from the very start.
Profiles are essential to the language's future, will not break existing code, and will not prevent a favorite new feature.
Stroustrup advised support for initial profiles in C++ 26, warning against incompatible, ad hoc restrictions as the alternative.
Collection
[
|
...
]