Currently a dist.toml can be a [workspace] but we'd like to instead make it so dist-workspace.toml can be a [package].
Constraints/goals:
for simple single-project cases you shouldn't have to make manifest files
don't want the gross distinction of cargo with "virtual" and "non-virtual" workspaces
want it to be easy to say which file to put something in
Right now we let a dist.toml be a defacto dist-workspace.toml but it can't have the workspace.members field. We should flip it around so that a dist-workspace.toml file is always the root, and if it doesn't have workspace.members it's assumed the current dir is a package, as if it were a dist.toml.
Gankra
commented
3 weeks ago
Currently a dist.toml can be a [workspace] but we'd like to instead make it so dist-workspace.toml can be a [package].
Constraints/goals:
Right now we let a dist.toml be a defacto dist-workspace.toml but it can't have the workspace.members field. We should flip it around so that a dist-workspace.toml file is always the root, and if it doesn't have workspace.members it's assumed the current dir is a package, as if it were a dist.toml.