-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
RFC: Cargo feature deprecation #3486
base: master
Are you sure you want to change the base?
Conversation
ec49bf1
to
0c803c3
Compare
0c803c3
to
6c3d1f4
Compare
The hope with these changes is to clarify what is there and not to change what the author intended.
[rationale-and-alternatives]: #rationale-and-alternatives | ||
|
||
WIP |
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.
Don't forget to close this out
[prior-art]: #prior-art | ||
|
||
WIP |
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.
Don't forget to close this out
- A `rust-version` field that could indicate e.g. `rust-version = "nightly"` or | ||
`rust-version = "1.65"` to specify a MSRV for that feature. See: | ||
<https://github.com/rust-lang/rfcs/pull/3416#discussion_r1174478461> |
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.
How is this related to deprecation?
- A `stable` field can be set false to indicate API-unstable or nightly-only | ||
features (something such as `stable = 3.2` could be used to indicate when a | ||
feature was stabilized). See also: | ||
<https://github.com/rust-lang/cargo/issues/10882> |
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.
How is this connected to this RFC?
```toml | ||
[features] | ||
foo = { enables = [], deprecated = true } | ||
foo = { enables = [], deprecated = "this works as a note" } |
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.
theres two foo
features, is that intentional?
Co-authored-by: Joe ST <[email protected]>
Rendered
RFC for
feature-deprecation
RFC goals: add a way to deprecate Cargo features
This was split from #3416
This would resolve rust-lang/cargo#7130