C++ opts for Profiles and leaves Safe C++ behind

"Safe C++ was intended as an optional context in which code would receive the same strong guarantees as in Rust. These include memory safety, type safety, and protection against race conditions. The idea was that existing code would continue to function as usual, while newly written or modified parts could run within a secure context. The proposal thus seemed to bridge the gap between current practice and a safer future for C++. Nevertheless, the concept remained controversial."

"According to Baxter, the Safety and Security Study Group preferred the so-called Profiles project. This initiative also aims to increase security, but does so through restrictions and rules that developers can voluntarily enable. Instead of introducing new language constructs, Profiles mainly impose compile-time restrictions. These are supplemented by a few runtime checks. Anyone who activates a profile commits to those rules, but without a profile, C++ continues to function as usual."

The Safe C++ proposal to add Rust-like guarantees to C++ will not be further developed, confirmed by one of its original authors. Safe C++ aimed to offer an optional context delivering memory safety, type safety, and protection against race conditions while leaving existing code unchanged. The Safety and Security Study Group favored the Profiles project instead. Profiles seek to improve security through voluntary compile-time restrictions and a few runtime checks rather than new language constructs. Bjarne Stroustrup has expressed support for Profiles. Critics say plans remain vague and implementations are not yet widespread. Committee votes showed support for Safe C++ but insufficient to advance it.

Read at Techzine Global