Check out the book on structs. It’s a solid resource for the second part of your question. This book is a solid intro to the concepts that you’ll need to understand moving to memory safety.
this post was submitted on 03 Mar 2024
24 points (100.0% liked)
Learn Programming
1625 readers
1 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
Thank you!
If it's a full-fledged model data type, I tend to put it into an own file. It will usually get various trait implementations, like for converting from other data types, so that the separate file makes sense.
Often, there's 'auxiliary' types, though. For example, I might have a function which takes a config object as parameter, which is only used there. Or it returns an enum of errors. In that case, I tend to define the types in the same file.
Generally, though, if you find yourself in a scrolling dungeon, that's when you break things up. You don't have to get things perfect from the start, because Rust's module system is pretty good for splitting up files without a massive refactoring.