New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracking Issue for Packages as (optional) namespaces #2457

Open

syphar opened this issue Mar 13, 2024 · 1 comment

Member

syphar commented Mar 13, 2024

RFC: #3243

rustc tracking issue: Tracking Issue for Packages as (optional) namespaces rust#122349
cargo tracking issue: Tracking Issue for Packages as (optional) namespaces cargo#13576
crates.io tracking issue: Tracking Issue for Packages as (optional) namespaces crates.io#8292

Allow a parent package to open its API namespace for other packages to participate

main points to be discussed / designed:

allow :: in crate names, nothing should break
allow navigation in the namespace (for example as a dropdown in the topbar, and/or as a section in the sidebar)
perhaps build namespace crates together to be able to search them together, similar to when dependencies are built with rustdoc default

The text was updated successfully, but these errors were encountered:

epage mentioned this issue

Tracking Issue for Packages as (optional) namespaces rust-lang/rust#122349

Open

9 tasks

epage commented May 22, 2024

For past discussion, see https://rust-lang.zulipchat.com/#narrow/stream/356853-t-docs-rs/topic/Namespace.20packages.2C.20rustdoc.2C.20and.20docs.2Ers

syphar mentioned this issue

Support multi-crate projects #2021

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment