[wolfadex]

A little history of why Rust's error messages look and read they way they do:

- [1] back in 2015 Elm puts out a blog post titled Compiler Errors for Humans

- [2] then another, Compilers as assistants

- [3] then in 2016 Rust announces they'll borrow from Elm for error messages

Really great that the students were able to see how much the Rust community cares about error message quality.

1. https://elm-lang.org/news/compiler-errors-for-humans

2. https://elm-lang.org/news/compilers-as-assistants

3. https://blog.rust-lang.org/2016/08/10/Shape-of-errors-to-com...

[asicsp]

And now Python seems to be following their footsteps: https://twitter.com/pyblogsal/status/1416034899639750659

[steveklabnik]

And importantly, ever since these events, keeping up the workflow described in the post: treating bad diagnostics as bugs, and having some hard-working, dedicated folks just grinding out the improvements. There is a looooong tail here.

[pjmlp]

Turbo Pascal also provided a nice experience, that I quickly missed when I moved into C and C++ world of endless error messages when a semi-colon is out of place.