#C++ Committee Divided on Memory Safety Plans

2 messages · Page 1 of 1 (latest)

civic axle
#

The C++ Standards Committee is struggling to implement memory safety features into the language due to conflicting interests and lack of participation.

https://thenewstack.io/c-committee-divided-on-memory-safety-plans/

  • The article discusses the challenges the C++ committee faces in implementing memory safety features, highlighting the lack of consensus and differing priorities among members.

  • While memory safety is a growing concern due to vulnerabilities that can lead to security breaches and system crashes, it isn't a top priority for the committee.

  • Multiple proposals have been put forward, such as Circle and Profiles, each offering different approaches to achieving memory safety.

  • The committee is exploring lessons from Rust, a language known for its strong memory safety, and has implemented some basic safety features in C++26.

  • The article also highlights the efforts of companies like Microsoft and Google in addressing memory safety issues in their products and the importance of moving towards safer programming practices.

  • Despite the challenges, the committee acknowledges the need for memory safety in C++ and is actively working towards a solution, though it might take a considerable amount of time to reach consensus.

Conflicting interests, differing priorities and lack of participation has stymied the passing of memory safety proposals for C++.

marble frigate
#

it might take a considerable amount of time

well… C++42