Tracking Issue for `--print=supported-crate-types`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for the compiler print request --print=supported-crate-types.
This print request is currently unstable, gated behind -Zunstable-options.
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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
Steps
- Draft and accept an MCP: https://github.com/rust-lang/compiler-team/issues/836
- Implement the print request as an unstable print option: https://github.com/rust-lang/rust/pull/138641
- Adjust documentation (see instructions on rustc-dev-guide): https://github.com/rust-lang/rust/pull/138641
- Stabilization PR (see instructions on rustc-dev-guide): TODO; after some baking
Unresolved Questions
- (Bikeshedding) Is
supported-crate-typesthe best name for the print request?
Design decision history
None yet, since initial implementation.
Implementation history
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the rustc-dev-guide stabilization guide and review the implementation PR #138641, the MCP in compiler-team issue #836, and the unresolved naming question. Confirm the print request has had sufficient baking and determine the stabilization steps. Done means a stabilization PR addresses the remaining checklist item and resolves or records the naming decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100