> It also doesn't tell us how rustc behaves on code that is being modified, which will be incomplete/broken/weird. Hmmm, good point. It also wouldn't tell you

> It also doesn't tell us how rustc behaves on code that is being modified, which will be incomplete/broken/weird. Hmmm, good point. It also wouldn't tell you what someone did before giving up because they would never commit code. Still, it's a useful data point. You could, say, time the build for the top 100 crates once a week, or gather metrics on language features that they use.