Call me a weirdo but the more errors a compilers give me the happier (albeit a bit frustrated) I am. That stuff generally surfaces in a way or another… and I prefer at compile time 🙂
That said I haven’t spent quality time with Rust yet… so not sure if there are a lot of nitpicks (ala go) or these are valgrind-level of “holy s*** I am so grateful to this tool” 😃
The borrow checker makes things a bit more complicated to get running, definitely takes some getting used to when you come from a non-memory safe language. But the compiler is really helpful throughout almost all mistakes, often directly providing an explanation and a suggested fix. One of my favorites programming experiences so far
The weird part of rust is replacing straight forward semicolons from other languages with the more verbose
.unwrap();.Just kidding, don’t lecture me about it.
?The amount of people on the internet seriously complaining that both Rust error handling sucks and that
.unwrap();is too verbose is just staggering.I think the problem is that many introductory examples use
unwrap, so many beginner programmers don’t get exposed to alternatives likeunwrap_orand the likes.
Learning C, that smasher would never have stopped.
It would also be emitting significantly less helpful messages.
“What messages?”
Lol yes
Segmentation fault?
