Re:A comparison of Rust's borrow checker to the one in C#
by galangalalgol on Friday November 01, 2024 @08:10AM
(#42016136)
You can still leak memory via a container. You can still create deadlocks. You can still throw a panic (with a backtrace). It does not solve the halting problem. But if it compiles you will not have any form of undefined behavior. No reading or writing out of bounds. No use after free, no dangling pointers, and no data getting modified across threads in an inconsistent way. If it needs a lock, the compiler will tell you with an error.
Re:A comparison of Rust's borrow checker to the one in C#
by radicalbyte on Friday November 01, 2024 @09:44AM
(#42016865)
> If it needs a lock, the compiler will tell you with an error.
Oh that's what I was getting at, that makes Rust pretty much a must-have tool to have in your tool-belt.
Haskell promises to solve concurrency and the Rust boys are always claiming that it's impossible to write buggy code in Rust.. and the jump from C/C++/C#/Golang to Rust is much smaller than to Haskell..