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

[email protected]

Data Structures in Rust (self.learn_programming)

submitted 7 months ago by 6eathaus to c/[email protected]

3 comments fedilink hide all child comments

What are some tips and tricks and best practices with rust?

Also, I'm used to clearly defined classes and implementation files with C++. Are there any tips and tricks on that with Rust? I haven't found any decent commentary/ documentation on figuring this out correctly with Rust. Yes, I know Rust is not an oop language, but I'm having issues creating clear separation of files so they don't become a scrolling dungeon.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 7 months ago

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.