Timeline for Result object vs throwing exceptions
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 15, 2020 at 17:12 | comment | added | Thorbjørn Ravn Andersen | @john16384 Interesting. Appears to have been added in Java 7, but I cannot find out why. Doing this will in my opinion sacrifice clarify for no good (to me) reason. | |
| Feb 15, 2020 at 17:04 | comment | added | john16384 | Java atleast allows you create exceptions without stacktraces and avoid the penalty (if that isn't a case of premature optimization in the first place) by disable writableStrackTrace. You can also create exceptions that are static (if the exception class is sufficient information to identify the problem) by making the exception immutable (writableStackTrace and enableSuppression both set to false) | |
| Feb 15, 2020 at 12:09 | history | edited | Thorbjørn Ravn Andersen | CC BY-SA 4.0 | added 2 characters in body |
| Feb 15, 2020 at 11:57 | history | answered | Thorbjørn Ravn Andersen | CC BY-SA 4.0 |