Open
Description
Unstable Feature Usage Metrics
Track unstable feature usage trends by Rust users.
Motivation
- Support feature stabilization prioritization.
- Helping teams know which unstable features to invest their energy into.
- Evaluating how representative crates.io is as a sample of the rust ecosystem (will we see different patterns in crates.io feature usage vs private feature usage?)
Context
Steps / History (PROVISIONAL)
- define the format the metrics will be stored in
- add flag to dump unstable feature status metrics (what features exist, if they're stable or not, both for library and lang/compiler, tidy may already support this for lib features)
- add flag to enable unstable feature usage metrics in the compiler
- front end to display reports based on gathered usage and status metrics
- back end to save metrics data from published crates.io crates (private data should be anonymous and stored separately once we have established the ability to gather that in a statistically relevant volume)
- integrate with docs.rs to have it gather metrics and upload them to the backend while building newly uploaded crate versions
Metadata
Metadata
Assignees
Labels
Area: MetricsCategory: An issue tracking the progress of sth. like the implementation of an RFCRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the language team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.