Re:Rust Moving Towards an IDE-Friendly Compiler with Rust An...
by pjmlp on Sunday February 02, 2020 @02:16PM
(#22218725)
I might be wrong on the origins, but I am certainly right that everyone else is now adopting similar algorithms.
So while it is great that Rust is making these concepts mainstream, in about 5 years time, the other languages will have their New Jersey style implementations mature and available for their communities.
Re:Rust Moving Towards an IDE-Friendly Compiler with Rust An...
by pcwalton on Sunday February 02, 2020 @02:22PM
(#22218781)
Borrow checking cannot be soundly added to C++, or most other languages, for systematic reasons. Soundness isn't a theoretical property here: C++ has constantly been adding things that make it safer as opposed to making it safe, and memory safety problems are still a huge issue.
See "Safe C++ Subset is Vaporware" by Robert O'Callahan: https://robert.ocallahan.org/2016/06/safe-c-subset-is-vapour...
Re:Rust Moving Towards an IDE-Friendly Compiler with Rust An...
by pjmlp on Sunday February 02, 2020 @04:25PM
(#22219548)
Why do you think I mentioned New Jersey style implementation?
Google and Microsoft are the ones driving that effort, in what concerns C++.
That vapourware is quite welcomed when using DriverKit, Unreal, COM/UWP, Project Treble drivers,..
The borrow checker is actually original, though based on known techniques. Specifically, the original part is that it allows the per-use-site choice of aliasing vs. mutability instead of making the decision globally.