On 12/29/2017 1:57 PM, rjframe wrote:
I noticed the Rust error has a code, too (E0308); if better error messages
are too difficult to implement, assigning codes to error types and
documenting them on the wiki could be helpful. Once you've dealt with an
error type, the messages aren't that bad, but having documentation for the
first time you run into it would be nice.
Many compilers produce such error codes. I've considered it many times, but
eventually concluded it added negative value.
1. Typing in an error code is so 1980's :-) People expect better these days.
2. A list of error messages with explanations can be trivially searched with a
simple 'find text' command, which is much easier than typing in an error code.
3. Ideally there'd be a url one could click on, not an error code.
4. It's ugly.
Somewhat-related question out of curiosity: is there ever a time the error
message "template instance foo!(bar) error instantiating" is actually
needed?
Yes. It shows where the error originates in the user's code.
