Multiple packages in a repository force a hierarchy

[SiegeLord]

In many cases it is convenient to have many packages per repository. For example, in one of my projects I have several library packages and several examples which use different subsets of that set of library packages to show how to use them together. Ideally, I'd make each example a separate binary package, but I find that having to place each one in a separate directory to be very noisy and inconvenient.

I'd prefer for that not to be required. Possible solutions include:

• Change Cargo.toml to package_name_here.cargo. This would allow multiple manifest files to coexist in the same directory. Has additional benefits of advertising the package name without needing to look into the file.
• Allow multiple packages per single Cargo.toml. This is possible because the TOML file format supports nesting sections.
• Same as above, but maybe add separate dependency lists for each [[bin]] section?

[alexcrichton]

This was a conscious decision when coming up with the current design, and as a result I'm going to close this issue for now. We may wish to revisit this design, but that will likely happen at a later date when we've gotten some more usage with the current scheme.