Repository navigation
Unstable Feature Usage Metrics #129485
Copy link
Copy link
Open
Labels
A-metricsArea: MetricsArea: MetricsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-langRelevant to the language teamRelevant to the language teamT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
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
A-metricsArea: MetricsArea: MetricsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-langRelevant to the language teamRelevant to the language teamT-libsRelevant to the library team, which will review and decide on the PR/issue.Relevant to the library team, which will review and decide on the PR/issue.
Activity
Rollup merge of rust-lang#130236 - yaahc:unstable-feature-usage, r=es…
Unrolled build for rust-lang#130236
Rollup merge of rust-lang#135844 - yaahc:tidy-feature-status-dump, r=…
Unrolled build for rust-lang#135844
yaahc commentedon Mar 3, 2025
As mentioned in rust-lang/goals#260 (comment), I need to have more detailed discussions with t-libs and t-lang to discuss specifics of unstable feature usage metrics and the precise questions t-libs and t-lang would likely like to use this data to answer.
@rustbot labels +I-libs-nominated +T-libs +I-lang-nominated +T-lang
Related conversation: https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/unstable.20feature.20usage.20metrics
Rollup merge of rust-lang#137827 - yaahc:timestamp-metrics, r=estebank
Rollup merge of rust-lang#137827 - yaahc:timestamp-metrics, r=estebank
Rollup merge of rust-lang#137827 - yaahc:timestamp-metrics, r=estebank
Unrolled build for rust-lang#137827
Rollup merge of #137827 - yaahc:timestamp-metrics, r=estebank
Rollup merge of #137827 - yaahc:timestamp-metrics, r=estebank