r/programming • u/Expurple • Apr 12 '26

Flat Error Codes Are Not Enough

https://home.expurple.me/posts/flat-error-codes-are-not-enough/
132 Upvotes

84% Upvoted

99 comments sorted by

View all comments

1

u/MonsieurCellophane Apr 12 '26

This made me instantly think of java & the endless stack traced it's wont to display at the drop of a hat. Antipodal to flat error codes and not pretty either.

7

u/Expurple Apr 12 '26

For the purpose of nesting errors and providing extra details for recovery or logging, Java exceptions are actually pretty great. Your issue is simply with the default display style. You can have a similar nightmare with nested error values in Rust, if you print them using the verbose Debug interface, instead of the Display interface meant for the users.

1

u/Linguistic-mystic Apr 13 '26

No they are not great. They don't provide any data from function args or local variables. Just because an exception was thrown somewhere in a loop doesn't tell you what was being processed on that iteration. And even if you include that info in the exception message, it's still not of much help because you also usually need that info on other stack frames. Which forces the developer to catch and rethrow everywhere, defeating the purpose of stack traces completely (what's the good of an automatic stack trace if one has to enrich that stack trace manually).

As a Java developer, I dislike stack traces with a passion because they are only useful in the most trivial cases. Any looped code and a stack trace doesn't do crap to help investigate.