-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Tracking Issue for multidep #10030
Copy link
Copy link
Open
Labels
C-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.S-needs-mentorStatus: Issue or feature is accepted, but needs a team member to commit to helping and reviewing.Status: Issue or feature is accepted, but needs a team member to commit to helping and reviewing.
Description
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.S-needs-mentorStatus: Issue or feature is accepted, but needs a team member to commit to helping and reviewing.Status: Issue or feature is accepted, but needs a team member to commit to helping and reviewing.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
In Progress
Summary
RFC: #3176
This is the tracking issue for RFC 3176 which extends Cargo to allow depending on the same crate multiple times with different dependency names, to support artifact dependencies for multiple targets.
This is a follow up to RFC #3028 tracking issue #9096.
Unresolved Issues
No response
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.