24
submitted 1 year ago* (last edited 1 year ago) by jpfreely@programming.dev to c/rust@programming.dev

I started off avoiding mod.rs because it's the old way and I prefer having the module name as the filename. However, if the module needs a folder for submodules anyway, then there's a reason to tuck it away as mod.rs, especially if not doing so leaves lots of duplicate names (a.rs, b.rs, c.rs, ..., a/, b/, c/).

But then I don't really like to have much else in mod.rs other than mod declarations and pub use. Maybe a utility fn or a not-unwieldly implementation of struct "Foo", the module's namesake.

you are viewing a single comment's thread
view the rest of the comments
[-] nous@programming.dev 5 points 1 year ago* (last edited 1 year ago)

But then I don't really like to have much else in mod.rs other than mod declarations and pub use.

You can always inline the mod.rs contents in its parent module and have one fewer file overall. Not every module needs to be in its own file.

But generally when working in an IDE I don't like to see a bunch of mod.rs files in the tabs as it just makes it harder to jump to the right one.

[-] UnshavedYak@kbin.social 1 points 1 year ago

I did that at work and people had a heart attack lol. Which i thought was silly because the mod literally had no code in it besides module file declarations. /shrug

this post was submitted on 13 Aug 2023
24 points (92.9% liked)

Rust

5966 readers
17 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

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