2 ms·
Their plan is twofold, in my understanding: first to translate the code fairly literaly, and then second, to provide unsafe -> safe refactoring tools. As far as
by steveklabnik 7y ago
Their plan is twofold, in my understanding: first to translate the code fairly literaly, and then second, to provide unsafe -> safe refactoring tools. As far as I know they’re still on step 1.
- K0nserv 7y agoCool, that seems like a very sensible approach. The fact that they are already uncovering memory issues in C is promising too.
- steveklabnik 7y agoYep, I think so too. That example output is more verbose than a human would write, but it’s a sensible start.
- harpocrates 7y agoStep 2 has been happening concurrently, and pretty much since the start of the project. See https://github.com/immunant/c2rust/tree/master/c2rust-refactor https://github.com/immunant/c2rust/tree/master/c2rust-refact.... It is just a lot tougher to get right, so it gets less publicity.
- steveklabnik 7y agoAh awesome! Thanks for the link.
- mikepurvis 7y agoLooks like it's meant to enable projects similar to how the Go compiler/toolchain was initially translated (with the like-named c2go) and then gradually rewritten over time into idiomatic golang. It's easy to see that this could be a much more tenable project then a grand rewrite that has two codebases iterating forward in parallel for a time.