C++ Nixes Rust‑Style Safety Model

The C++ standards committee chose to prioritize 'Profiles'—guideline‑enforcing subsets—over a proposal for a Rust‑like 'Safe C++' that would add borrow‑checking and strict safety annotations. Backers say this forecloses a path to Rust‑level memory safety within C++, leaving incremental, opt‑in profiles rather than enforced safety semantics. Given C++’s footprint in infrastructure and products, the decision affects how (or whether) legacy codebases can meet rising safety expectations. — This choice will influence cybersecurity risk and the feasibility of public and corporate pushes for memory‑safe software across critical systems.