""Yes, work on Safe C++ within ISO has been discontinued," Bott said September 29 in response to an InfoWorld email inquiry. The C++ Safety and Security SG/EWG (Study Group/Evolution Working Group) committee prioritized safety profiles from Stroustrup instread, Bott said. The poll was 19 for Profiles, nine for Safe C++, 11 for both, and six neutral. "Profiles moved forward as an incremental, backward‑compatible path feasible for C++26 timelines," Bott said."
""By contrast, Safe C++ did not reach committee consensus and was seen to imply fundamental redesign and high specification/implementation risk, with broad ecosystem‑migration concerns. Profiles were also viewed as the fastest practical response to regulatory pressure for memory safety." Thus C++ safety work continues via Profiles and related library and tooling efforts in the committee. Safe C++ extensions were intended to offer C++ developers memory-safe implementations of essential data structures and algorithms, along with features that prevent common memory-related errors."
Work on Safe C++ extensions within ISO has been discontinued. The C++ Safety and Security SG/EWG committee prioritized Bjarne Stroustrup's safety profiles as an incremental, backward-compatible path feasible for C++26. Committee voting favored Profiles (19), Safe C++ (9), both (11), and neutral (6). Safe C++ was judged to require fundamental redesign, pose high specification and implementation risk, and raise broad ecosystem-migration concerns. Profiles were viewed as the fastest practical response to regulatory pressure for memory safety. A key Safe C++ advocate stopped working on the proposal late last year.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]