Unresolved: How many levels of crate-namespace nesting is allowed?

[carols10cents]

Both theoretically for any registry that might exist, and practically for what crates.io will allow.

[Manishearth]

The current RFC sticks to one level, but we should design it for multiple IMO so the restriction is easily lifted later.

The main places this will come up:

• registry trie format
• feature syntax (Unresolved: Feature syntax #4)
• crates.io and docs.rs backend code

[ShadowJonathan]

An initial suggestion; 8 levels.

It should be quite sufficient for all kinds of purposes, be long enough where nobody could be hitting the limit with natural growth, and be small enough to be efficiently contained in the backend code.

[jsgf]

What's the use-case for deeply nested namespaces? If a namespace corresponds to an organization or owner, then do we want to support (effectively) shipping the org chart?

[Manishearth]

I don't think there has been yet.

Two levels may be useful, one to represent an overall project and another to represent sub-crates (like project::foo and project::foo::derive)