Recent searches
Search options
My coworkers ask for help with a #Rust compiler error... *once*...
...and then I run and try to mechanize my explanation and put it back in the compiler.
Our dev tools need to talk to humans in the way humans talk. Nobody is an expert on everything, helping newcomers (with better tools, better docs, better errors) helps *everyone*.
That's really the trick behind the rustc diagnostic output: it's not about a technology, its an attitude.
rustc doesn't have good diagnostic messages because of some technological breakthrough. It has good diagnostic because we look at how people use our tools, noticing when things confuse people, and changing the output to match people's mental model.
@ekuber I would boil it down to "it has good diagnostics because a bunch of people really care about it and put in a lot of effort".
@nnethercote indeed. It's a ratched effect: people who care about it work on it, which attracts people who care about it, who in turn notice the things that aren't yet great. The bar is constantly raised, what passed for great yesterday is expected today and will be considered subpar tomorrow.