-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Provide a way to get feedback on compiler error rates #45857
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
Comments
I think we better keep
|
@kennytm those sound like solid arguments to me |
Rustup already has a config flag for telemetry. rust-lang/rustup#341 |
Oh in this case the entire thing can be implemented on top of rustup's |
I don't believe that we've done anything in this area in the past few years. |
I've formalized some of my thoughts on the matter: https://estebank.github.io/rustc-metrics.html |
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 inrustc
/cargo
, to a simple webapp accepting people to post compiler output. Right now the only ways we receive feedback for confusing output are: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.The text was updated successfully, but these errors were encountered: