Work on a project called Safe C++ extensions, which aimed to make C++ safer by preventing common memory errors, has come to a halt. The company overseeing the project, the C++ Alliance, confirmed that they stopped working on it in favor of another approach suggested by Bjarne Stroustrup, the creator of C++.

The Shift from Safe C++ Extensions to Safety Profiles

The Safe C++ extensions were meant to add features that would help developers write more memory-safe code. This would include safer data structures and algorithms that reduce bugs related to memory handling. The idea was to make C++ more secure without changing its core design too much.

However, the C++ community and the standards committee decided to focus on safety profiles instead. These profiles are sets of rules and best practices that help programmers avoid memory mistakes while keeping compatibility with existing code. This approach is seen as easier to implement and more practical for the language’s future.

The decision was based on a poll of the committee members. About 19 members favored safety profiles, nine supported Safe C++, 11 liked both, and six remained neutral. The safety profiles were viewed as a way to improve safety incrementally, fitting into the timeline for C++ 26, expected in 2026. This version of C++ aims to include new features like compile-time reflection, which makes the language more powerful and easier to use.

Reasons Behind the Change in Direction

The committee believed that Safe C++ would require a complete redesign of parts of the language and pose significant risks for implementation. It could also cause issues for developers and tools that rely on older versions of C++. Because of these challenges, the committee favored safety profiles, which offer a more gradual and compatible way to improve safety.

Bjarne Stroustrup, who created C++, supports this approach. He argues that safety is a broad concept that can be addressed through profiles, rather than trying to implement a one-size-fits-all safety layer. Stroustrup pointed out that Safe C++ only focused on memory safety and would have eliminated many safe, high-quality C++ programs.

Sean Baxter, an advocate for Safe C++, said he stopped working on the project last year when it became clear that the committee was moving away from it. Meanwhile, Stroustrup criticized Safe C++ for its narrow focus, saying it would remove many good, safe C++ features instead of improving them.

The ongoing development of C++ is now centered around the safety profiles, along with updates to libraries and tools that support safer coding practices. The goal is to make C++ more secure without risking widespread disruption or losing the language’s existing strengths.

In summary, the future of C++ safety enhancements has shifted from a bold, all-encompassing extension to a more incremental, profile-based approach. This decision aims to balance safety improvements with the practical needs of the C++ community and the upcoming features planned for C++ 26.

Inspired by

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

Sources

• gmpg.org
• cppalliance.org
• safecpp.org
• herbsutter.com
• podigee.com