Introduce additional execute methods for ResilienceStrategy

Introduce ExecuteValueTaskAsync methods for ValueTask-based callbacks (both void and T based):

• (ResilienceContext, State)
• (ResilienceContext)
• (State, CancellationToken)
• (CancellationToken)

Introduce ExecuteAsync methods for Task based callbacks (both void and T based):

• (ResilienceContext, State)
• (ResilienceContext)
• (State, CancellationToken)
• (CancellationToken)

Introduce Execute methods for synchronous callbacks (both void and T based):

• (ResilienceContext, State)
• (ResilienceContext)
• (State, CancellationToken)
• (CancellationToken)
• (State)
• ()

[PeterCsalaHbo]

Well, they are not exactly the same because you have made the context creation and context passing explicit. I think, it is an acceptable workaround. I’ve just wanted to highlight with the example that ExecuteAndCapture can be useful in implicit context passing.

IMHO keeping the API small and focused is a better design goal than supporting a case where a workaround is also acceptable. So, I’ve just wanted to get an answer whether the AndCapture overloads are left out intentionally or accidentally.

[martintmk]

@PeterCsalaHbo

Just for comparison the same thing done with V8:

public static class ContextExtensions
{
    private static readonly ResiliencePropertyKey<int> key = new("RetryCount");

    public static void IncreaseRetryCount(this ResilienceContext context)
    {
        context.Properties.Set(key, context.GetRetryCount() + 1);
    }

    public static int GetRetryCount(this ResilienceContext context)
    {
        if (context.Properties.TryGetValue(key, out int count))
        {
            return count;
        }

        return 0;
    }
}

var strategy = new ResilienceStrategyBuilder()
    .AddRetry(2, TimeSpan.FromSeconds(10), args => args.Context.IncreaseRetryCount())
    .Build();

var context = ResilienceContext.Get();
strategy.Execute(_ =>DoSomething(), context);
var retries = context.GetRetryCount();

Of course, we can add more convenience overloads based on the feedback.