Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

telemetry service that tabulates top warnings, complaints #8161

Closed
graydon opened this issue Jul 31, 2013 · 3 comments
Closed

telemetry service that tabulates top warnings, complaints #8161

graydon opened this issue Jul 31, 2013 · 3 comments
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@graydon
Copy link
Contributor

graydon commented Jul 31, 2013

This is a bit of a weird / wishlist item, but it would be nice to be able to gather statistics on how often our users hit which errors, and how much they like them vs. loathe them.

This would be a relative of #2092 in which we have a code reserved for each warning/error/lint message (which we never reuse). Rustc would be configured to keep local tabulation in your homedir while you work of a few basic statistics (codebase size, number of unique files processed, number of runs of the compiler, resource usage) and the number of occurrences of a given message, along with a pair of commands (say: rustc yay and rustc boo) that mark your approval or disapproval of the most recent error message. Periodically, or on demand, you could submit your tabulated set to a telemetry service. This way we could get directed feedback of the sorts of problems people are having while using the compiler as well as whether they appreciate or feel annoyed by various forms of error message.

(Other suggestions welcome; was thinking win vs. fail, or perhaps some variant of derp, wat or fuuuuuu but couldn't think of suitable paired positive-affirmation phrases, and in any case they seem a little unkind.)

@brson
Copy link
Contributor

brson commented Jan 10, 2014

This is a pretty cool idea.

@brson
Copy link
Contributor

brson commented Feb 9, 2014

I would be happy just to get a log of all errors codes emitted to start.

@steveklabnik
Copy link
Member

I'm pulling a massive triage effort to get us ready for 1.0. As part of this, I'm moving stuff that's wishlist-like to the RFCs repo, as that's where major new things should get discussed/prioritized.

This issue has been moved to the RFCs repo: rust-lang/rfcs#629

flip1995 pushed a commit to flip1995/rust that referenced this issue Jan 13, 2022
…, r=camsteffen

Improve documentation for `borrowed-box` lint

fixes rust-lang#8161

Updates documentation to elaborate more on how removing Box from a function parameter can generalize the function.

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Development

No branches or pull requests

3 participants