5 ms·
> Although, I'm more amazed this post has been up an hour without any rust comments.. I've actually thought "WTF why porting a project to a memory unsafe langu
by pizza234 5y ago
> Although, I'm more amazed this post has been up an hour without any rust comments..
I've actually thought "WTF why porting a project to a memory unsafe language", but actually the PR title is somewhat excessive - it's more of a modernization, indeed described by the author as "the first incremental step of getting libtransmission to compile with a C++ compiler".
- phkahler 5y agoI think there is a tool to automatically convert C to Rust, but that would probably be a terrible idea given what looks like a lot of custom data structures that would translate to unsafe Rust.
- Ericson2314 5y agoIt would be interesting to try to make it recognize C++ STL usage but not much more of C++ next.
- junon 5y ago> WTF why porting a project to a memory unsafe language Because proper handling of memory is actually quite easy to achieve in C++ assuming you're doing all the right things. We also have great tooling for this a la sanitizers and valgrind. Also, C and C++ remain to be more performant than Rust in the general case, and don't require rewriting everything into a completely different paradigm.