Timeline for How to report multiple compilation errors?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 15 at 1:06 | comment | added | ivanjermakov | Regarding last paragraph: it might not be useful for compiler, but for the langauge server it is extremely useful to report as much diagnostics as possible (with some certainty of correctness). LSP showing a single syntax error on missing semicolon is a bad LSP. | |
| Jul 13, 2023 at 6:46 | comment | added | Eric Lippert | The point made in your last paragraph is important but it might not be clear to the reader why "there's no point". A germane example: if the "is there a cycle in the base classes" checker produces an error, then that's a great time to stop looking for more errors because code that reports, say, illegal conversions probably assumes that the type hierarchy is acylic. If you bail out early then you don't need to make later error passes safe to analyze wrong programs! | |
| May 16, 2023 at 23:26 | history | edited | kaya3 | CC BY-SA 4.0 |
added 4 characters in body
|
| May 16, 2023 at 23:18 | history | answered | kaya3 | CC BY-SA 4.0 |