3 ms·
You get safe programming for “free” in Rust. So those 400 pages mentioned are not equivalent to what you glean from the intro to C book. It’s not a fair compari
by bluejekyll 9y ago
You get safe programming for “free” in Rust. So those 400 pages mentioned are not equivalent to what you glean from the intro to C book. It’s not a fair comparison.
Edit: fixed pronoun referencing gp...
- rurban 9y agoNo, Rust is not safe. From the 3 fundamental safeties: memory, concurrency and types, Rust only provides type safety.
- steveklabnik 9y agoWhat do you mean? Memory and concurrency safety are so important that they're in the main slogan of the language.
- Ar-Curunir 9y agoRust has the first two, and a rather strong type system, which is soon getting the equivalent of higher minded types, putting it roughly on par with Haskell in that respect. How much stronger do you want your type systems to be?
- syrrim 9y ago>You get safe programming for “free” in Rust. Not really. Rust will tell you your program is unsafe at compile time, whereas c will tell you at runtime. The major difference is that c sometimes won't tell you about an unsafe program, whereas rust will call perfectly safe programs unsafe. Note that for a beginner, the former is vastly preferable, because it allows them to iterate much faster. It doesn't matter if your code is buggy if you throw it away, and it doesn't matter if your code has security bugs if it will never be worth hacking.