46
Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
(opensource.googleblog.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Jun 2023
46 points (97.9% liked)
Rust
5960 readers
2 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 1 year ago
MODERATORS
Matches my experience with rust as well. Once I got used to some of the concepts and syntax, everything started to just fall into place.
Same here. It's been 1-2 months and I feel pretty comfortable.
That's great to hear, my experience way back when I have learned Rust was a little bit more rough (though still nice), and I think it took longer for me to get really comfortable (language server (at that time "rls") was far not as good as rust-analyzer is now).
Yes, I started off with a C mindset and had a bit of a struggle the first days until the mental model of ownership and borrowing landed, after that it is mostly learning to use new concepts like pattern matching, the ? operator aso.
I've done some elixir so pattern matching and functional programming was pretty familiar but yeah, borrowing took me actually reading about it rather than going "I can just figure this out" before I was like "Oh, that makes sense."
And yeah, I remember the first time I encountered the ? operator in some example code I was like WTF?!??! How do I search for THAT?
Having programmed in C, I got the ownership model quite fast. I just think of it as "is this function going to do an implicit free on return", if not then it should just borrow it. And for C, you already had to think of ownership, just that it was not enforced in any way in the language... if you messed up the ownership to either got a crash or leak.