I avoid using mod.rs because then I’ll have a bazillion mod.rs files. It’s what I hate about python modules. I would rather have a thingy.rs and then a thingy folder than many files named the same thing distinct only by their path.

I use mod.rs because I prefer having all the module’s files in the same folder. But I don’t do that unless a module is multiple files.

It varies, depending on if I have submodules or not. I see no reason to have a folder with a single mod.rs.

I use mod.rs because I like having a module entirely contained in its own directory, rather than having part of it in the parent one. Obvious exception is when the module does not have submodules.

It also follows the same structure of crates, where mod.rs maps to lib.rs. It has the (minor) advantage that I can trivially extract a module into its own crate by copying the module’s directory and renaming mod.rs to lib.rs, but more than anything I like the homogeneity.

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.

Same.

My mod.rs only contains a sequence of pub use self::...;.

For a moment in time, I rather disliked mod.rs files.

Then my editor got an update to show the folder name in tabs, when two files were named the same.

Now I am using mod.rs in my own code bases, because I want all related files in one place. ¯\_(ツ)_/¯

I use mod.rs all over the place because it entirely encapsulates a module in a folder. But since the name of the file is fairly obtuse and doesn’t say what it is, I usually only re-export other better named files that also exist in that folder.

I’m the case that I want a module with content, and then more further nested content that may use pub(super), I will use a module named file and a separate folder to hold it’s children modules.