[API Proposal]: AsyncContext for cancellation and ConfigureAwait

[alrz]

Background and motivation

To avoid passing cancellation and ConfigureAwait in every callsite, there's room to use async local to propagate the value for all the subsequent call sites.

API Proposal

Extracted from #94620 (comment)

public static class AsyncContext {
  public static void PushConfigureAwait(bool capture);
  public static void PushCancellationToken(CancellationToken token);
  public static bool ContinueOnCapturedContext { get; }
  public static CancellationToken CancellationToken { get; }
  public static void PushContext<T>(T context); // possibly a user-defined context
  public static T GetContext<T>();
}

Popping the value would be done internally.

API Usage

AsyncContext.PushConfigreAwait(false); // calling at the start of the program would make all tasks to not capture the context.

Alternative Designs

No response

Risks

No response

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-system-threading-tasks
See info in area-owners.md if you want to be subscribed.