Rust: Provide a way to get feedback on compiler error rates

Created on 8 Nov 2017 · 6Comments · Source: rust-lang/rust

As per https://github.com/rust-lang/rust/pull/45452#issuecomment-339329308, 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.

A-diagnostics C-enhancement T-compiler metabug

Source

estebank

👍2

Most helpful comment

I think we better keep rustc untouched, and telemetry (the post request sender) is better belong on cargo:

the "flag" can be part of ~/.cargo/config so you don't need to opt-in everytime
the "flag" can be configured when you install rustup the first time
rustc remains free of any network code
cargo already needs to connect to the internet (outside of airplane mode)

kennytm on 8 Nov 2017

👍6

All 6 comments

I think we better keep rustc untouched, and telemetry (the post request sender) is better belong on cargo:

the "flag" can be part of ~/.cargo/config so you don't need to opt-in everytime
the "flag" can be configured when you install rustup the first time
rustc remains free of any network code
cargo already needs to connect to the internet (outside of airplane mode)