You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: text/3692-feature-unification.md
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,15 @@ Supporting excludes adds environment/project configuration complexity as well as
114
114
115
115
This field will not apply to `cargo install` to match the behavior of `resolver.incompatible-rust-versions`.
116
116
117
+
The `workspace` setting breaks down if there are more than one "application" in
118
+
a workspace, particularly if there are shared dependencies with intentionally
119
+
disjoint feature sets.
120
+
What this use case is really modeling is being able to tell Cargo "build package X as if its a dependency of package Y".
121
+
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)).
122
+
While a solution that targeted this higher-level need would cover more uses cases,
123
+
there is a lot more work to do within the design space and it could end up being more unwieldy.
124
+
The solution offered in this RFC is simple in that it is just a re-framing of what already happens on the command line.
0 commit comments