Hello,
I often ask myself this question: wouldn’t it be more ergonomic to publish a Workspace as a whole, like, for example, a super-crate? Often, Rust libraries contain several internal sub-crates, but when we publish a project, they end up being published one by one as independent crates. This clutters the site and makes searching more difficult, especially when these sub-crates are intended for internal use.
What do you think?
This is what my RFC 3452: Nested Cargo packages was intended to do. However, it turned out to be quite complex in the details of how it would have to work. Myself, I am currently waiting to see how the accepted RFC 3243 packages as namespaces turns out — that will enable the internal crates to be at least explicitly grouped with their parent, even if not fully hidden, and we will see what makes sense from there.
Thank you for this information; I hope they find a good compromise. 