Hacker News new | ask | show | jobs
by nutheracc 3612 days ago
Yes, agreed, the Rust error messages are very helpful. Failure to understand the messages is a lack of familiarity with Rust, not a problem with the error messages.
2 comments

> Failure to understand the messages is a lack of familiarity with Rust

You could have said the exact same thing of G++'s pages of template error messages. That's indictment not praise.

If you must be highly familiar with the language to understand the compiler's error messages you might as well remove the messages altogether and just print "?" as ed(1) does, developers familiar with the language obviously don't need them and beginners apparently aren't allowed to understand them so why even bother?

(good thing the Rust developer team disagrees with your vision of the subject).

You are trying to catch on words, but it's just not true. I went my way from the 0-noob in Rust to comfortable using and I can say compiler errors were always helpful. Always. From the very beginning of my journey.
> You are trying to catch on words

No. I'm clearly replying to a clear opinion, there's no catch although I might be exaggerating very slightly.

> but it's just not true.

What is not true?

> I went my way from the 0-noob in Rust to comfortable using and I can say compiler errors were always helpful.

That's got nothing to do with the comment you're replying to.

To me, an error message should help in understanding the language better. It shouldn't impose a requirement to have the knowledge beforehand.
Each compiler error message in Rust have special code, using it you can find article with detailed explanation how things work, targeted to beginners.
That'll surely attract the beginners, such efforts by the Rust team and the whole community are truly laudable.