6 ms·
Translating it back to C or C++ afterward, it would be equally as safe, and easier to deploy.
by angiosperm 2y ago
Translating it back to C or C++ afterward, it would be equally as safe, and easier to deploy.
- maximilianburke 2y agoThat would only work if the C code was treated as a generated artifact and not touched directly. If the C code is worked on directly it will be just as susceptible to unsafe changes as before.
- acdha 2y agoComparably easy to deploy perhaps but easier? Is there some scenario you have in mind where that would be worth the overhead of that complex extra step?
- pornel 2y agoRust projects are pretty easy to deploy. It's just LLVM underneath, and the product is similar to clang-built code. You get a library, static or dynamic, that you can link with anything that can link with C. Rust projects are much easier to build, especially when supporting multiple platforms. I've converted projects to Rust to make them easier to build and deploy.
- johnisgood 2y agoDoes Cargo re-use dependencies today? Last time I tried to build medium-sized Rust projects, it pulled hundreds of dependencies each time, even the same ones. It took up too much space, and took too long to build.
- steveklabnik 2y agoYes, and it always has. If you do a second build, it will not rebuild those dependencies again. > even the same ones. Rust supports multiple versions of the same dependency, so that may be what you observed.
- johnisgood 2y agoYeah, I believe it was that.