3 ms·
Sadly, it won't teach you what happens if you fail to consider something. This means, long hours of tracing, debugging, leak checks etc. The lesson is: never
by AstralStorm 11y ago
Sadly, it won't teach you what happens if you fail to consider something.
This means, long hours of tracing, debugging, leak checks etc.
The lesson is: never ever rely on compiler, framework, language or other potentially buggy tools to think for you. Even with Rust's "hard" approach, you can get complacent and hemorrhage performance and memory until there's no turning back.
Those things were written by fallible people without hard mathematical proof everywhere, after all. Rust and especially its libraries too.
Understand libraries, their implementation and design trade-offs if you're using them.
- lossolo 11y agoInteresting, could you give some example of such Rust code?
- pcwalton 11y ago> This means, long hours of tracing, debugging, leak checks etc. But you don't have undefined behavior to debug, and that makes debugging easier. Trying to reverse engineer from a corrupted memory dump from a production system what the compiler did to your code and relate that back to where it went wrong is something you will have to do in C++, given enough time. You don't have to do that in Rust.