Skip to content

Unstable Feature Usage Metrics #129485

Open

Description

@yaahc

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

Activity

  1. added
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Aug 23, 2024
  2. added
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on Aug 23, 2024
  3. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    and removed
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on Aug 23, 2024
  4. added a commit that references this issue on Nov 21, 2024
  5. added a commit that references this issue on Nov 21, 2024
  6. added a commit that references this issue on Feb 4, 2025
  7. added a commit that references this issue on Feb 4, 2025
  8. yaahc commented on Mar 3, 2025

    @yaahc
    MemberAuthor

    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

  9. added
    I-lang-nominatedNominated for discussion during a lang team meeting.
    I-libs-nominatedNominated for discussion during a libs team meeting.
    T-langRelevant to the language team
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    on Mar 3, 2025
  10. added 2 commits that reference this issue on Mar 5, 2025
  11. added a commit that references this issue on Mar 6, 2025
  12. added a commit that references this issue on Mar 7, 2025
  13. removed
    I-libs-nominatedNominated for discussion during a libs team meeting.
    on Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-metricsArea: MetricsC-tracking-issueCategory: 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.T-langRelevant to the language teamT-libsRelevant to the library team, which will review and decide on the PR/issue.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions