Recent searches
Search options
@me this is what veilid was implemented in. And we will always have MOO
@screwtape Yeah, Veilid is the reason I'm choosing to use Rust in the first place. The last time I read the documentation, I was generally able to understand the concepts (at least in theory). I just didn't really have a project in mind to put that learning into practice, so much of it has faded.
If I can learn Haskell though, I'm sure I can learn Rust.
@me @screwtape when I first looked at rust, the concepts in the docs made sense but writing code was difficult. I put it down for 6 months and when I came back the curve was more natural. I think there's just a necessary bake period for the consequences of the simple concepts and their interactions to become intuitive, practical, applicable patterns. Main piece of advice I'd give is "keep calm and call clone". It will look "inefficient", but it will get you unstuck to learn the rest of the lang.
@ekuber @me @screwtape Do you still find it necessary to use clone a lot? I resisted -- not on the basis of efficiency, but wanting to understand the language's approach to handling memory -- and found it wasn't often needed.
So, options for newcomers include:
1. The "steep route": avoid cloning until you learn to work "with the grain" of the borrow checker.
2. The "gentler route": clone liberally until you're comfortable with the rest of the language, and then try to understand ownership.