Timeline for Are very explanatory compiler error messages worth the effort needed to implement them?
Current License: CC BY-SA 4.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2023 at 12:11 | comment | added | gidds |
A counterexample: “A friend of mine in a compiler-writing class produced a compiler with one error message ‘You lied to me when you told me this was a program’.” — Pete Fenelon. And a more widely-available one: by default, the Unix line editor ed indicates all errors by displaying a single ?, as ‘the experienced user will know what is wrong’ (though later versions can show more descriptive error messages on request).
|
|
| Jul 8, 2023 at 3:53 | comment | added | Justin Time - Reinstate Monica |
If you wonder whether they're worth the effort, just try to troubleshoot errors relating to, say, something going wrong with std::string, std::vector, and/or std::ostream in C++ (or with template types in general), or especially troubleshooting anything that involves SFINAE. Error messages can easily devolve into borderline gibberish if you don't know how templates work, and even then they can still be hard to parse, and that's with compilers trying to make them helpful. I'd hate to imagine what it'd be like with anything less helpful!
|
|
| S Jul 1, 2023 at 16:16 | history | suggested | Karl Knechtel | CC BY-SA 4.0 |
be more precise in the title
|
| Jul 1, 2023 at 14:49 | review | Suggested edits | |||
| S Jul 1, 2023 at 16:16 | |||||
| May 22, 2023 at 13:46 | vote | accept | Spevacus | ||
| May 19, 2023 at 8:21 | review | Close votes | |||
| May 19, 2023 at 8:28 | |||||
| May 19, 2023 at 3:42 | answer | added | Michael Homer♦ | timeline score: 10 | |
| May 19, 2023 at 1:57 | answer | added | Ray Butterworth | timeline score: 7 | |
| May 19, 2023 at 1:53 | history | edited | Spevacus | CC BY-SA 4.0 |
added 404 characters in body
|
| May 19, 2023 at 1:29 | answer | added | Pseudonym | timeline score: 15 | |
| May 19, 2023 at 1:21 | history | reopened |
pppery Bbrk24 lyxal♦ Spevacus Isaiah |
||
| May 19, 2023 at 0:54 | review | Reopen votes | |||
| May 19, 2023 at 1:21 | |||||
| May 19, 2023 at 0:33 | history | closed |
CPlus Ginger mousetail 'he-him' The Thonnu Redz |
Opinion-based | |
| May 18, 2023 at 16:55 | review | Close votes | |||
| May 18, 2023 at 17:48 | |||||
| May 18, 2023 at 14:38 | comment | added | felipecrv | "going so far as to point out the specific portion of a line that's problematic" is the minimum I would expect from any compiler that's meant to be used these days. It's not that hard to put a ^~~~~ below the errors in your compiler messages. Regarding suggestions, that could be done later and you could start with simple variable name typo suggestions. | |
| May 18, 2023 at 14:15 | answer | added | kaya3 | timeline score: 16 | |
| May 18, 2023 at 14:14 | comment | added | Seggan | Python recently is getting Rust-esque error messages as well | |
| May 18, 2023 at 14:09 | answer | added | pppery | timeline score: 14 | |
| May 18, 2023 at 13:51 | history | asked | Spevacus | CC BY-SA 4.0 |