5 ms·
An Update on Memory Safety in Chrome
- miohtama 5y agoBecause Chrome is a massive legacy C++ codebase, going back to WebKit’s root in KDE, here is Chrome team documentation how much existing C++ APi can be interoperated from Rust and what kind of bridges need to build: https://www.chromium.org/Home/chromium-security/memory-safety/rust-and-c-interoperability https://www.chromium.org/Home/chromium-security/memory-safet...
- axiosgunnar 5y agoSince speed is one the main selling points of Google Chrome, option 2 (C++ runtime checks) is not a long term solution, is this article basically a (purposefully) muffled announcement hinting at „We will be rewriting Google Chrome in Rust“?
- jamesfinlayson 5y agoLooks like it. Not surprising that they investigated borrow checking in C++ though as rewriting Chrome is much more than a big job.
- pjmlp 5y agoclang and Visual C++ support borrow checking in their C++ static analysers. However it is pretty much a proof of concept with plenty of false positives on their current state.
- axiosgunnar 5y ago> rewriting Chrome is much more than a big job What is it then?
- jamesfinlayson 5y agoA risky, probably decade-long proposition.
- axiosgunnar 5y agoI see