{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihn5syg5bcfemugk462x7cgnziv7s6jnzqrtob655wwx26u7cl3e4",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkkllqmm7qi2"
  },
  "path": "/t/pre-rfc-dns-domains-as-package-namespaces/24202?page=2#post_38",
  "publishedAt": "2026-04-28T12:05:48.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "DragonDev1906:\n\n> Is there any reason not to be able to use an already published crate as a namespace(parent)? That way we don't need a separate naming system and in many cases this is also what you want (e.g. `tokio-util` could be at `tokio@util` ). In that case namespaces would be more like child-crates (possibly even allowing `parent@child@subchild` if desired.\n\nNote that there is an already approved rfc for using packages as namespaces but it serves a slightly different role where the packages truly compose into one API. There will be impedance mismatches if used for organizational namespacing, This is covered in the namespacing thread I linked earlier.",
  "title": "[Pre-RFC] DNS domains as package namespaces"
}