# Child Thread: Survey of registry namespace designs for Cargo and Crates.io

**URL:** <https://internals.rust-lang.org/t/child-thread-survey-of-registry-namespace-designs-for-cargo-and-crates-io/24030>\
**Category:** cargo\
**Created:** [February 20, 2026, 10:25pm UTC](https://internals.rust-lang.org/t/child-thread-survey-of-registry-namespace-designs-for-cargo-and-crates-io/24030 "2026-02-20T22:25:47Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Vorpal](https://avatars.discourse-cdn.com/v4/letter/v/aca169/32.png) [@Vorpal](https://internals.rust-lang.org/u/Vorpal)\
**Post date:** [February 21, 2026, 9:50am UTC](https://internals.rust-lang.org/t/child-thread-survey-of-registry-namespace-designs-for-cargo-and-crates-io/24030/4 "2026-02-21T09:50:28Z")

</div>

You have hit on an important point (both here and in the other thread at [Child Thread: Survey of organizational ownership designs for Cargo and Crates.io - #2 by kornel](https://internals.rust-lang.org/t/child-thread-survey-of-organizational-ownership-designs-for-cargo-and-crates-io/24028/2)): the real world is messy, and simple hierarchical designs rarely work.

Perhaps it would be better to _not_ go down the route of hierarchical namespaces or ownership at all. Tag systems tend to be more flexible and reflect reality better. I don't know what such a design would look like in detail for this case (tag based namespacing sounds... difficult), but perhaps it is something worth thinking over.

---

_[View the full topic](https://internals.rust-lang.org/t/child-thread-survey-of-registry-namespace-designs-for-cargo-and-crates-io/24030)._