Result<Result<T>> and the absence of Bind

[megasuperlexa]

Is there any reason to not have Bind for Result?
I am now ended up writing numerous Match (success => new Result(TransfromSuccessToResultOfAnotherT()), err => new Result<AnotherT>(err)) methods instead of simply Binding my transformation.

[aloslider]

You need to bind Trys, not Results:

Try<T> tryT = () => default(T);
Func<T, Try<AnotherT>> tryAnotherT = (T t) => () => MapTToAnotherT(t);
Try<AnotherT> operation = tryT.Bind(tryAnotherT);

[StefanBertels]

This might be helpful, too:

#1226

[megasuperlexa]

This might be helpful, too:

#1226

Thanks. I wish it was more articulated, e.g. via the[Obsolete] attribute.

[louthy]

Because of the endless confusion about Result, I have removed it from v5.0.0 -- Fin is recommended (as has already been stated by other commenters)