The documentation for Task.WhenAny in the async programming guide was causing confusion for readers who couldn't understand the difference between "the two tasks" mentioned in the explanation. The issue was that the explanation didn't clearly distinguish between:

1. The wrapper Task<Task> returned by Task.WhenAny
2. The actual completed task contained within that wrapper

Changes Made

Updated the explanation in the "Apply await expressions to tasks efficiently" section to more clearly explain:

• That Task.WhenAny returns a Task<Task> - a wrapper task that contains the completed task
• The difference between awaiting the wrapper task vs awaiting the actual completed task
• Why you need to await the completed task again (to access results and handle exceptions properly)

Before

The `await Task.WhenAny` expression doesn't wait on the finished task, but rather waits on the `Task` object returned by the `Task.WhenAny` method. The result of the `Task.WhenAny` method is the completed (or faulted) task.

After

This line is important because `Task.WhenAny` returns a `Task<Task>` - a wrapper task that contains the completed task. When you `await Task.WhenAny`, you're waiting for the wrapper task to complete, and the result is the actual task that finished first.

The new explanation uses clearer language and explicitly mentions the Task<Task> wrapper concept to help readers understand why there are "two tasks" involved and why both await operations are necessary.

Fixes #44497.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Internal previews