Comment by samus
11 days ago
That's not how "unsafe" works at all. If "unsafe" is so commonplace in a code base that your statement becomes relevant then the project is badly run, and memory safety is just another problem among many others. Similar to accepting code with empty or nonsensical `catch` blocks.
> Similar to accepting code with empty or nonsensical `catch` blocks.
You can still find a lot of that in production code though. You're imagining a perfect world where everyone does the correct thing, but id that world existed we would need rust in the first place
People using a tool in the wrong way is not necessarily an argument against the tool though. There's always the potential for misuse. (Of course, this misuse should be sharply distinguished from the errors caused by my memory-unsafe features since those will reliably cause errors even if programmers are careful)
> People using a tool in the wrong way is not necessarily an argument against the tool though
Apart from when that tool is a memory unsafe language though...
Isn't rust as a replacement to c one of the central selling points of rust? Ie the tool is crap because people are misusing it
1 reply →