dnrops
/
rfcs
mirror of https://github.com/rust-lang/rfcs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

alt: Build X as if its a dependency of Y

This commit is contained in:
Ed Page 2024-10-03 13:43:10 -05:00
parent 969cb03e43
commit a071fe46da
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
text/3692-feature-unification.md
View File

@ -114,6 +114,15 @@ Supporting excludes adds environment/project configuration complexity as well as
This field will not apply to `cargo install` to match the behavior of `resolver.incompatible-rust-versions`.
The `workspace` setting breaks down if there are more than one "application" in
a workspace, particularly if there are shared dependencies with intentionally
disjoint feature sets.
What this use case is really modeling is being able to tell Cargo "build package X as if its a dependency of package Y".
There are many similar use cases to this (e.g. [cargo#2644](https://github.com/rust-lang/cargo/issues/2644), [cargo#14434](https://github.com/rust-lang/cargo/issues/14434)).
While a solution that targeted this higher-level need would cover more uses cases,
there is a lot more work to do within the design space and it could end up being more unwieldy.
The solution offered in this RFC is simple in that it is just a re-framing of what already happens on the command line.
# Prior art
[prior-art]: #prior-art