Here's a subtle thing I like about Rust.

Rustc has what are, in my opinion, best-in-class error messages. Several people have written crates for generating error messages like rustc.

As a result, most Rust tools I'm running into, particularly those that parse a language, have error messages roughly as good as Rustc. Like the (still-experimental) Filament HDL, whose error message are already yards better than Bluespec: https://filamenthdl.com/docs/lang/tutorial.html

I <3 good error messages.

#rust

Your First Filament Program - Filament

@cliffle virtuous feedbacks beget vituous feedbacks. People expect more, so they simultaneously demand and give more. I hope that it continues spreading to more and more places.
@ekuber @cliffle It's so important I use this tweet in academic talks that aren't about Rust at all.

@jedbrown @ekuber supporting this view -- there are several languages where I never figured out how to find the generated code, and _only_ used the error output.

Agda, for instance. Never did figure out how to run an Agda program, but I sure did evaluate some fancy proofs at compile time.