3 ms·
The question is, how do you modularise yourself codebase enough to write chunks of it in Rust and not C++? Take a massive codebase like Libreoffice. How would
by chris_wot 4y ago
The question is, how do you modularise yourself codebase enough to write chunks of it in Rust and not C++?
Take a massive codebase like Libreoffice. How would you even start to migrate this to Rust?
- Kelteseth 4y agoIsn't that exactly what Mozilla did with Stylo? https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-engine-quantum-css-aka-stylo/ https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-en...
- oncewas 4y agoIn a lot of cases I would consider a staged rewrite. Ie, I would turn what I could into dylibs going either from rust to c++ or c++ to rust. Assuming the code has structure and isn't infinite singletons and free standing functions this can make more or less sense. I'd translate the parts with the most likelihood for memory safety or thread safety issues first, so the transition could be part of the release cycle. It would still be a lot of work, but you might see benefits at intermediate releases this way.