The Safe C++ extensions proposal, aimed at improving memory safety in the language, has been discontinued. The plan was rejected in favor of safety profiles from C++ founder Bjarne Stroustrup.

According to Harry Bott, CEO of the C++ Alliance, work on Safe C++ has ceased. The proposal was intended to provide C++ developers with memory-safe implementations of essential data structures and algorithms, along with features that prevent common memory-related errors.

The Controversy Surrounding Safe C++

Stroustrup was critical of the Safe C++ proposal, disputing the notion that it was a subset of C++. He argued that the plan would eliminate almost all good/safe C++ code and only addressed memory safety.

Sean Baxter, a key advocate of the Safe C++ proposal, said he stopped working on the plan late last year. The C++ committee acted quickly to express that this wasn’t the preferred way forward, Baxter stated.

C++ 26 and the Future of Memory Safety

The C++ 26 version of the language is expected to be feature-complete in 2026. The release includes features such as compile-time reflection, which is expected to improve the way code is written and expand the expressiveness of the language.

Stroustrup’s safety profiles were prioritized over Safe C++, with a poll showing 19 votes for Profiles and nine votes for Safe C++. Profiles were seen as an incremental, backward-compatible path feasible for C++26 timelines.

The Path Forward for C++ Safety

C++ safety work continues via Profiles and related library and tooling efforts in the committee. The C++ Alliance has ceased work on the Safe C++ proposal, but the issue of memory safety remains a pressing concern for the language.

With the release of C++ 26 just around the corner, it’s clear that the future of memory safety in C++ will be shaped by Stroustrup’s safety profiles. Whether this approach will prove effective remains to be seen.

The discontinuation of the Safe C++ proposal highlights the challenges of improving memory safety in a language as complex and widely used as C++. As the language continues to evolve, it’s likely that the issue of memory safety will remain a contentious topic among developers and committee members alike.

Inspired by

• https://www.infoworld.com/article/4065702/safe-c-proposal-for-memory-safety-flames-out.html

Sources

• cppalliance.org
• safecpp.org
• herbsutter.com