3 ms·
> . It is im fact the solution, and a solution that's being ignored. If the coder's C++, that is written in flow without being distracted by borrow-checkers an
by kazinator 8y ago
> . It is im fact the solution, and a solution that's being ignored.
If the coder's C++, that is written in flow without being distracted by borrow-checkers and whatnot, is in fact correct code, then no, there is no solution that is being ignored; what's being ignored is a "problem in search of a solution".
> Or is anyone expecting that your memory corruption problems will magically cease because you write your same old memory allocation and access bugs in Rust instead of C or C++?
That's a pretty good executive summary of the Rust cheerleading.
In fact, what you describe is sometimes possible. For illustration, let's confine our attention to use-after-free bugs and memory leaks. If we make the free function do nothing, and stick in a garbage collector, then in fact you can write (some of) "your same old memory allocation and access bugs" yet they are mitigated.