Tracking Issue for Metrics Initiative #128914
Labels
-Zmetrics-dir
Unstable option: metrics directory
A-diagnostics
Area: Messages for errors, warnings, and lints
A-metrics
Area: Metrics
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
D-diagnostic-infra
Diagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
The Metrics Initiative
This is a tracking issue for the Metrics Initiative. 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, please:
Please file dedicated issues for specific concerns that you wish to register. Discussions or concerns become very hard to track on GitHub issues once they reach more than a couple of comments, and GitHub's UI will then collapse discussions.
Context
rustc
produce a local log of execution metrics compiler-team#679Motivation
Excerpt from the Council Zulip thread as summary (edited by me):
Guiding Aims
Suggested Use Cases
TODO
Concerns and Related Issues
Related Labels
Implementation History
The text was updated successfully, but these errors were encountered: