4 ms·
> ... and it's very dangerous, we'll see ton of new developers thinking their software is safe because the borrow checker didn't complain Would new developers
by SubjectToChange 4y ago
> ... and it's very dangerous, we'll see ton of new developers thinking their software is safe because the borrow checker didn't complain
Would new developers be capable of writing secure C?
- Kukumber 4y agoNo, but that's not the point of C The problem is Rust advertise itself as a safe language due to the borrow checker, wich is a false and dangerous claim
- brundolf 4y agoThere are different definitions of safety If what you mean by "safe" is "memory-safe", then you're wrong. It is definitely truthful to say that Rust code is guaranteed memory safe (within safe code sections, barring compiler bugs, etc). If what you meant by "safe" is "bug-free", then it never claims to guarantee that your code is free of bugs- that would be nonsense (though it does a lot to help out!), and I don't think people would get that idea.