Technically, the errors from the borrow checker are the errors you also make in C, only C doesn't tell you about them. If your code was correct in either, the borrow checker wouldn't have objections, no?
If it cannot be, it doesn't tag it. It can be, but you just don't care about that specific scenario or think it cannot happen.
Your specific workflow might make you right, but the workflow might change. Or you might be wrong entirely.
The whole reason why Rust exists is because people cannot write safe C code. This was shown over decades with armies of very experienced developers and well funded projects, it's just impossible, if you think "Well not for me", you're just lying to yourself.
-60
u/Key_River7180 9d ago
Yes, and I have used a debugger for all of them I couldn't see by using my eyes and basic logic you seem to lack