-
Notifications
You must be signed in to change notification settings - Fork 2.7k
docs: Remove statement that dep features are optional #15408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
r? @weihanglo rustbot has assigned @weihanglo. Use |
// https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html. | ||
"req": "^0.6", | ||
// Array of features (as strings) enabled for this dependency. | ||
// May be omitted since Cargo 1.84. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you = give a concrete example of the failing case, and the step to produce?
@rustbot author |
Reminder, once the PR becomes ready for a review, use |
The current wording (from rust-lang#14839) makes it sound like new Cargo doesn't care about the `features` entries when in reality Cargo does care still, the field is just defaulted. Closes rust-lang#15408
The current wording (from rust-lang#14839) makes it sound like new Cargo doesn't care about the `features` entries when in reality Cargo does care still, the field is just defaulted. Closes rust-lang#15408
The current wording (from rust-lang#14839) makes it sound like new Cargo doesn't care about the `features` entries when in reality Cargo does care still, the field is just defaulted. Closes rust-lang#15408
I created my own registry by using a git repo and found that leaving the
features
in the dependencies in an index entry does not work. When a crate A has dependencies with features and you try to use it via the registry in crate B the build fails when A uses symbols only available by said features.I tested with with 1.86