3 ms·
> If you're fighting the borrow checker in Rust, you'd probably have been fighting segfaults and use-after-free in C / C++. That is in my ( admittedly limited)
by lawl 5y ago
> If you're fighting the borrow checker in Rust, you'd probably have been fighting segfaults and use-after-free in C / C++.
That is in my ( admittedly limited) experience just not true. There's plenty of things that are perfectly safe that the borrow checker just doesn't understand.
The borrow checker can prove that a subset of things is safe. But the borrow checker being unable to prove something doesn't mean it's not safe.
- giovannibajo1 5y agoThis, one thousands times. The borrow checker forces you to write in the very narrow subset of code paradigms it can understand. When it fails to compile, it doesn't mean it's wrong: it means that it can't prove that it's correct, which is a completely different statement.