3 ms·

Correct. There is probably a model for checked exceptions that is good but it's current state in Java isn't it. Kotlin did the right thing by not implementing

• masklinn 5y ago
  > There is probably a model for checked exceptions that is good but it's current state in Java isn't it. Yeah and Java has pretty thoroughly poisoned that well so in every discussion of the concept what comes up is mostly Java’s implementation and then it’s dead on arrival. And then you’ve got Swift which uses an exception-ish syntax for results, but they’re not even remotely exceptions, and functions must say that they are faillible (or failure-transparent) but then can’t say what their failures are, so it always feels like the worst of both worlds. Though it makes more sense when you understand that it’s dual to the old `NSError*` out-parameter system.