Re:Compiler Errors for Humans (2015)
by Existenceblinks on Thursday November 24, 2022 @02:00PM
(#33735032)
I seem to have an unpopular opinion about humanized compiler error messages. It's better than cryptic messages for sure but I think it's worse than robotic but concisely clear error messages. For example, for a type error, don't write mini book for me, just tell me "line: 56 column: 97, s/int/string/". Same for complicated error, don't try to be human it's even more confusing.
[ Parent
| on HN ]
> line: 56 column: 97, s/int/string/
Sorry, but that’s the least accessible error message I have ever read.
Re:Compiler Errors for Humans (2015)
by capableweb on Thursday November 24, 2022 @03:50PM
(#33736077)
You haven't dealt with PHP by any chance, have you?
Not saying the above is good/bad, just saying that there are (was) worse offenders out there for sure.
Re:Compiler Errors for Humans (2015)
by Existenceblinks on Thursday November 24, 2022 @04:42PM
(#33736558)
Half serious, I think JS' "undefined is not a function" wouldn't be terrible if it tells me where it lost its value. The message itself is already ok.
Re:Compiler Errors for Humans (2015)
by Existenceblinks on Thursday November 24, 2022 @04:21PM
(#33736361)
I suspect the downvoter misinterprets my "example". s/int/string/ meant to be semantics. Something like diff in test or text diff with semantic help.
Re:Compiler Errors for Humans (2015)
by cloogshicer on Thursday November 24, 2022 @02:46PM
(#33735444)
Out of genuine curiosity: Why do you think that? Trying to understand where you're coming from.
Re:Compiler Errors for Humans (2015)
by Existenceblinks on Thursday November 24, 2022 @04:17PM
(#33736340)
I wrote Elm before and while the error message is nice it takes longer to iterate and fix stuff. Because It's in a mix mode of docs and error message. I only want a clear error message concisely.
Re:Compiler Errors for Humans (2015)
by cloogshicer on Thursday November 24, 2022 @05:09PM
(#33736796)
Interesting, thanks for explaining.