How We Replace Common C and C++ Libraries
summary
Google reports >70% of severe C/C++ bugs stem from memory safety and replaces risky third‑party libraries with Rust alternatives, using Rust Shift (AI‑assisted C/C++→Rust translator with differential fuzzing and formal verification) for ports like GIF Flip RS, and Crouton to generate bidirectional C++/Rust FFI when APIs differ. Practical issues include differing decoder behavior, tiny pixel/precision mismatches, and occasional internal patches; solutions: leniency heuristics, upstream collaboration with Image RS maintainers, and open‑sourced bindings deployed at scale.
AI-written summary · about
related talks
04m"Scaling Safety: Rust at Google”
45mThe existential threat against C++ and where to go from here
41mWe can have nice things
01h 01mMemory Safety: Rust vs. C
42mRewrite It In Rust: Can We RIIR Everything?
28mC2Rust: Migrating Legacy Code to Rust
53mFrom Chaos to Control: Overcoming C and C++’s Inherent Unsafety
15mTranslating C to Safer Rust