3 ms·
Rust newbie here. If you're working on a project like that, how bad (or even possible) would it be to just stick unsafe around almost everything, if the altern
by quietbritishjim 7y ago
Rust newbie here.
If you're working on a project like that, how bad (or even possible) would it be to just stick unsafe around almost everything, if the alternative is to use C++? I mean, unsafe Rust is still no worse than C/C++, right?
- probably_wrong 7y agoIn my case, I wouldn't do it for two reasons. First, if the whole point of using Rust is "memory safety", then writing everything unsafe would be missing the entire point. I'd rather do it well at some time in the future, when I properly understand the language. Which leads me to my second point: at this point, I'd rather do it in C (which I did). I haven't done much C lately, but I'm at least aware of its strengths, weaknesses, and best practices. Better to use an old tool well than a new one badly. More expert Rust programmers can probably give a better answer.