4 ms·
> or b) just use Rust to extend and piecemeal replace old apps (since it supports linking to C and/or C++ libs). Yes, Rust's FFI support is nice, but rewriting
by duneroadrunner 10y ago
> or b) just use Rust to extend and piecemeal replace old apps (since it supports linking to C and/or C++ libs).
Yes, Rust's FFI support is nice, but rewriting piecemeal is still rewriting. (And retesting.) It should be faster and easier to just replace unsafe elements in existing code. Of course, that doesn't conflict with choosing Rust for new components and rewrites of existing components when the time and resources are available.
Btw, I haven't investigated lately, what is the state of Rust interoperability with C++ interfaces?
- kbenson 10y ago> Btw, I haven't investigated lately, what is the state of Rust interoperability with C++ interfaces? Not that I'm an expert on the matter, I think it's still through C interop both directions. There was a github project for a Rust module submitted to HN recently[1] to correctly deal with C++ name mangling, and I think it was mentioned that the plan is for it to eventually be used as part of the future C++ interop plans, but I could be misremembering. 1: https://news.ycombinator.com/item?id=13706799 https://news.ycombinator.com/item?id=13706799