Investigate whether a PotentialRecovery class makes sense

[theangrydev]

Like the PotentialFailure class but for sad recoveries

[tjheslin1]

How would this work? I imagine you'd define a HappyPath type you could flow back into and a SadPath type in which you would stay in?

[theangrydev]

Just like HappyPath.attempt(ActionThatMightFail<Happy, Sad> actionThatMightFail) can go from happy to sad based on the PotentialFailure<Sad> result of the ActionThatMightFail, I can imagine a SadPath.attempt(ActionThatMightRecover<Happy, Sad> actionThatMightRecover) that can go from sad to happy based on a PotentialRecovery<Happy> result of the ActionThatMightRecover.

It would probably just be a copy-paste job to implement, based around the existing happy attempt method and everything it depends on. There might be a better name than "attempt" too I can't think of one right now though.

What do you think?

[tjheslin1]

"attempt" is good. I would avoid "retry" as I can imagine uses other than retrying.

I've heard you use "recover" before which I think is general enough but is a hint at its intended usage.