-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Open
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-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.metabugIssues about issues themselves ("bugs about bugs")Issues about issues themselves ("bugs about bugs")
Description
As per #45452 (comment), and other conversations that have been had over time, there's a feeling that we should have ways of identifying what rustc
features are being used/encountered. This can range from full featured telemetry support in rustc
/cargo
, to a simple webapp accepting people to post compiler output. Right now the only ways we receive feedback for confusing output are:
- IRC/gitter
- this issue tracker
- stackoverflow
- /r/rust
If we added telemetry support on rustc, it would also have to be opt-in, and it could start with being a simple flag passed to rustc
to send a post request with the text output of the compiler. These reports could then be aggregated by type.
euclio and oli-obk
Metadata
Metadata
Assignees
Labels
A-diagnosticsArea: Messages for errors, warnings, and lintsArea: Messages for errors, warnings, and lintsC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-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.metabugIssues about issues themselves ("bugs about bugs")Issues about issues themselves ("bugs about bugs")