-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Highlight enables features in cargo info
#14634
Labels
C-enhancement
Category: enhancement
Command-info
S-triage
Status: This issue is waiting on initial triage.
Comments
georgmu
added
C-bug
Category: bug
S-triage
Status: This issue is waiting on initial triage.
labels
Oct 2, 2024
epage
added
C-enhancement
Category: enhancement
Command-info
and removed
C-bug
Category: bug
labels
Oct 2, 2024
epage
changed the title
cargo info does not correctly display enabled features
Highlight enables features in Oct 2, 2024
cargo info
That was stale information and we've only been supporting The question is which set of features to be considered enabled
And what should we do when the package isn't depended on by you? |
I have no experience with multiple workspace members, but here is what I expect:
(BTW: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-enhancement
Category: enhancement
Command-info
S-triage
Status: This issue is waiting on initial triage.
Problem
As described in #14141, the following thing should be displayed for features:
The enabled/disabled features are ignored in the
cargo info
output. There is always just a "+" for default features. Enabled features via Cargo.toml are not displayed as enabled.Steps
Possible Solution(s)
No response
Notes
No response
Version
cargo 1.83.0-nightly (80d82ca 2024-09-27)
release: 1.83.0-nightly
commit-hash: 80d82ca
commit-date: 2024-09-27
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w 11 Sep 2023
os: Fedora 41.0.0 (FortyOne) [64-bit]
The text was updated successfully, but these errors were encountered: