Comment on Canonical backs new project to translate large C codebases into safe RustComments−jedisct122dHave you heard about fil-c?−Tuna-Fish22dIt's an interesting option for infrastructure that's not performance critical.I agree with Domen Kožar that I want an extern "fil-c" in Rust. https://domenkozar.com/2026/08/13/i-want-extern-fil-c/−actionfromafar22dThat would be amazing. A C to Rust port could start out with Rust with only a fn main() at first, then progressively moving more and more stuff "up" from the C program into Rust, making it faster and faster.−nu11ptr22dIt is a massive accomplishment and neat tool for sure but:1) Induces a large performance penalty2) Introduces a GC into C code bases (higher memory requirements, performance profile changes)3) Is x86-64 only atm I believeAn idiomatic Rust port would have none of these issues, so it would be more a stop gap measure than a long term strategy.−Almondsetat22dWhat about it?
Comments
Have you heard about fil-c?
It's an interesting option for infrastructure that's not performance critical.
I agree with Domen Kožar that I want an extern "fil-c" in Rust. https://domenkozar.com/2026/08/13/i-want-extern-fil-c/
That would be amazing. A C to Rust port could start out with Rust with only a fn main() at first, then progressively moving more and more stuff "up" from the C program into Rust, making it faster and faster.
It is a massive accomplishment and neat tool for sure but:
1) Induces a large performance penalty
2) Introduces a GC into C code bases (higher memory requirements, performance profile changes)
3) Is x86-64 only atm I believe
An idiomatic Rust port would have none of these issues, so it would be more a stop gap measure than a long term strategy.
What about it?