Of course not the type system isn't strong enough to be generic over exceptions for lambdas. Swift has a pretty cool implementation of generic lambdas for typed throws.
public func count<E>(
where predicate: (Element) throws(E) -> Bool
) throws(E) -> Int {
print("Code goes here")
return 0
}
When your lambda doesn't throw it just turns into throws(Never)
I just feel that Java need to stop shipping things that perfectly fine could be libraries and just fix this elephant in the room. Ok, Valhalla and then error handling. Structured concurrency somewhat could be just figure out by the community for now
I whole heartedly agree, I extensively use checked exceptions everywhere and even without fixing the type system there are so many easy wins to make them more usable (imo, and brian will of course disagree). Checked exceptions just have so much boilerplate. Little things like Swift's try? and try! operators would be so beneficial.
Edit: formatting is fucked on this. I’ll have to fix it once I’m at a computer.
Of course.
try! or !! to automatically uncheck a checked exception when you can’t handle it. Right now you need to write several lines for this:
Something s;
try {
s = fn();
} catch (SomeException ex) {
throw new IllegalStateExceprtion(ex);
}
Something s = try! fn();
try? to automatically coerce into null:
Something s;
try {
s = fn();
} catch (SomeException _) {
s = null;
}
Something s = try? fn();
// combine that with the null operator
Something s = try? fn() ?? default();
8
u/javaprof 4d ago
So checked exceptions doesn't work properly here too?
This is very funny: