Re:Four limitations of Rust's borrow checker
by summerlight on Tuesday December 24, 2024 @04:12PM
(#42504947)
This is because programming is not a work in a continuous solution space. Think in this way; you're almost guaranteed to introduce obvious bugs by randomly changing just a single bit/token. Assembler, compiler, stronger type system, etc etc all try to limit this by bringing a different view that is more coherent to human reasoning. But computation has an inherently emergent property which is hard to predict/prove at compile time (see Rice's theorem), so if you want safety guarantee by construction then this discreteness has to be much more visible.
[ Parent
| on HN ]
There are no comments on this comment yet.