Add ifSuccessOrElse method to Try for unified handling of success or failure cases

[vesav-mms]

No description provided.

[SuppieRK]

Hey @vesav-mms! Thanks for the PR.

I think I understand the intent behind the change, and I believe that it goes against the functional API approach.

Can you provide your opinion as to why this change should be merged with an example of the use case you are trying to achieve?

[vesav-mms]

Intention is to be able to do following operations that otherwise do not look straight forward that are possible:

 Try.of(...)
        .ifSuccess(....)
        .ifFailure(...);

Basically, I want to turn operations like the following one that is not that intuitive in the construct above.

 var try = Try.of(...);
 try.ifSuccess(....);
 try.ifFailure(...);

[SuppieRK]

@vesav-mms as I suspected.

Instead of implementing these operations like you propose, how about we implement method:

void ifSuccessOrElse(ThrowableConsumer<? super T> valueConsumer, ThrowableConsumer<Throwable> throwableConsumer)

, which would follow the same logic as ifPresentOrElse​ method from Java 9 Optional?

My reason to avoid having the ability to chain for ifSuccess and ifFailure is to keep the semantic close to Java Optional, as well as preventing scenarios which will force these methods to act like a peek:

Try.of(...)
        .ifSuccess(....)
        .ifFailure(...)
        .map(...)
        .filter(...)
        .ifSuccess(....)
        .ifFailure(...)

[vesav-mms]

@SuppieRK changes done!