Re:Checked exceptions: Java’s biggest mistake (2014)
by mlk on Friday September 11, 2020 @12:28PM
(#24444436)
I absolutely agree, a checked exception is pretty much a Either<Exception, RESULT>, it only has a different (arguably ugly) syntax, I don't get all the hate. A "sufficiently intelligent compiler" could have turned signature with throws declarations in signature returning Either<Exception, T> but the hivemind has spoken and checked exception were simply ignored (see Scala and Kotlin)
[ Parent
| on HN ]
Re:Checked exceptions: Java’s biggest mistake (2014)
by ragnese on Friday September 11, 2020 @12:47PM
(#24444609)
Kotlin made the worst mistake here. At least Scala actually gives you ways to do error handling somewhat ergonomically with for comprehensions. Kotlin gives us nothing. Sure, you're "supposed" to return sealed classes and match on them. But it's so tedious and non-obvious that I've literally never seen it done in any Kotlin code I've depended on.
Re:Checked exceptions: Java’s biggest mistake (2014)
by benjiweber on Friday September 11, 2020 @04:14PM
(#24446865)
They're so similar you can easily translate between the two e.g. https://github.com/unruly/control/blob/master/src/test/java/...