Pass custom exception handlers in unchecked() and lift() about throwing-function HOT 4 OPEN

Good idea. Targeting 2.0.0 :)

from throwing-function.

But then, how can the user of the API deduce a replacement return value R from the thrown Exception object.

I don't see any type of relation between the exception being thrown and and the new replacement return value to use instead.

In the case of a ThrowingFunction<T, R, E extends Exception>, we can use a BiFunction<T, Exception, R> as a customer exception handler, in this case the user has the T and the Exception thrown to decide of the new R value to return.

We can even help the user by giving him precise context and use a BiFunction<T, E, R> as a custom exception handler, but then we need to do some type of unchecked cast to cast the exception thrown to E before calling the exception handler.

from throwing-function.

Adding the T to the exception handling is a good idea.

from throwing-function.

Giving empty exception handler we'll be able to ignore the exception [evil.jpg]. That's what I'm looking for, instead of this:

items.forEach(e -> {
try { e.delete(); } catch (Exception ex) {}
});

But this is also a case for such functionality:

items.stream().map(e -> {
    try {
        e.delete();
        return true;
    } catch (Exception ex) {
        return false;
    }
}).collect(Collectors.toList());

from throwing-function.