Tracking Issue for deprecating per-build-target edition field
#15283
Labels
A-edition-next
Area: may require a breaking change over an edition
A-editions
Area: edition-specific issues
C-tracking-issue
Category: A tracking issue for something unstable.
Comments
ehuss
added
the
C-tracking-issue
This was referenced Mar 8, 2025
epage
added
A-editions
epage
added a commit
to epage/cargo
that referenced
this issue
Mar 10, 2025
Leaving off any talk of it being removed until we know the edition. This is the first step in implementing rust-lang/rfcs#3772 (tracking issue rust-lang#15283)
epage
added a commit
to epage/cargo
that referenced
this issue
Mar 11, 2025
Leaving off any talk of it being removed until we know the edition. This is the first step in implementing rust-lang/rfcs#3772 (tracking issue rust-lang#15283)
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 11, 2025
### What does this PR try to resolve? This is the first step in implementing rust-lang/rfcs#3772 (tracking issue #15283) ### How should we test and review this PR? Leaving off any talk of it being removed until we know the edition. ### Additional information
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 18, 2025
### What does this PR try to resolve? This is a part of #15283 In the RFC, I mentioned this might be blocked on #12235. In hindsight, the use of this is [rare enough](https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/Deprecate.20build-target.20.60edition.60.20field.3F/near/499047806) that I suspect we can go ahead and warn without user controllable lints. ### How should we test and review this PR? ### Additional information
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
RFC: #3772
Implementation:
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/cargo-targets.html#the-edition-field
This feature is to deprecate the
editionfield in the cargo target configuration.Unresolved Issues
Future Extensions
No response
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
The text was updated successfully, but these errors were encountered: