Struct names conventions

[josecelano]

Sometimes I use the mod namespace to improve the readability, for example:

pub struct Entry {
    pub peers: std::collections::BTreeMap<peer::Id, peer::Peer>,
    pub completed: u32,
}

Notice the peer::Id and I would probably use the Entry with torrent::Entry.

But It seems the automatically generated crate documentation (with cargo doc) removes the namespaces:

so from my point of view, you can not rely on namespaces to improve readability because docs would not take advantage of that technique.

Should we stop using the namespace as a prefix @da2ce7 @WarmBeer ? For example:

pub struct Entry {
    pub peers: std::collections::BTreeMap<PeerId, Peer>,
    pub completed: u32,
}

If we do so, we have a problem with Clippy, we would have to extra the PeerId into its mod otherwise, it would complain because the struct has the same prefix as the mod name.

I'm used to one-class-one-file organization that other languages impose on you or because they have community conventions.