Description
Proposal
The -Z binary-dep-depinfo feature is extremely useful for identifying direct and transitive dependencies of a rustc command. In practice, this has been used to identify all inputs needed to execute rust compiles/links remotely. This feature generates a complete dep-info file, not just one that lists source files. This effectively adds redundant (harmless) transitive dependency edges.
Proposal is to make this behavior the default, so all dep-info files list their transitive dependencies.
This was also proposed on https://internals.rust-lang.org/t/support-zbinary-dep-depinfo-long-term/15253.
Mentors or Reviewers
[anyone]
Process
The main points of the Major Change Process are as follows:
- File an issue describing the proposal.
- A compiler team member or contributor who is knowledgeable in the area can second by writing
@rustbot second.- Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a
-C flag, then full team check-off is required. - Compiler team members can initiate a check-off via
@rfcbot fcp mergeon either the MCP or the PR.
- Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a
- Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.
You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.