Recent discussions surrounding C++ memory safety have highlighted projects like TrapC and Safe C++. Bjarne Stroustrup, the original designer of C++, asserts that safety can be enhanced through the use of profiles, which impose necessary restrictions without disrupting existing code. In a communication to the ISO C++ committee, Stroustrup expressed urgency in establishing a flexible profile framework within C++, advocating for initial implementations by C++26. He warned that failing to act could lead to a decline in the language's usability and safety.
C++'s type and resource safety, including memory safety, were aims of C++ from the very start, and profiles are crucial for maintaining this.
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 are essential for the language's future, will not break existing code, and are part of a long tradition of C++ evolution.
Support for initial profiles in C++ 26 is critical, and we must avoid incompatible, ad hoc restrictions as the alternative.
Collection
[
|
...
]