I feel that it's a future of compilers: it almost feels like in interactive session, where you can actually learn stuff. I suggest expanding this.

Have you heard of Idris? It's tagline is programming as a conversation.

To be fair--and I say this as a Rust fan--the pages of inscrutable error messages caused by a misplaced parenthesis in a template are pretty much over. Clang spearheaded this change to the point where some companies would use clang for development and gcc for production builds.

This isn't to say that template errors are problem-free but the situation is much better than it was 5 years ago.

I didn't mean it as slight against C++ template errors.

Java is my daily professional development. That's the baseline. And it's errors are not good as Rust's.

I often joke that IntelliJ IDEA is better programmer than I am. But in Rust, the same can be said of the Rust compiler.

The amount of suggestions, and explanations is stellar.

But you were adding to the parent's list, which was giving reasons to move from C++ to Rust.

I said, don't forget as in extra reasons to prefer it. It was 100% unrelated to C++ errors.

It's so helpful that it's jarring when it's not - hah.

Ie, i tried out Diesel for a few projects and after several months, i'm moving away from it. The compiler messages can be insane due to Diesel's rather.. excessive use of generics haha.

Just curious, but what are you replacing diesel with?

SQLx - unfortunately using some blocking wrappers for (currently) some non-async codebases.

SQLx has been really nice so far. I recommend it.