Skip to content

What happens when one of the argument tasks throws an exception is unclear #11350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
VesperGarment opened this issue May 25, 2025 · 1 comment
Labels
area-System.Threading.Tasks untriaged New issue has not been triaged by the area owner

Comments

@VesperGarment
Copy link

Type of issue

Typo

Description

Several times in this article it says:

The returned task will always end in the RanToCompletion state with its Result set to the first task to complete. The result value is true even if the first task to complete ended in the Canceled or Faulted state.

This seems wrong. The result value isn't true - it's the first task to complete, as it just said.

I think it should say:

The returned task will always end in the RanToCompletion state with its Result set to the first task to complete. This is true even if the first task to complete ended in the Canceled or Faulted state.

Page URL

https://learn.microsoft.com/en-us/dotnet/api/system.threading.tasks.task.whenany?view=net-9.0

Content source URL

https://github.com/dotnet/dotnet-api-docs/blob/main/xml/System.Threading.Tasks/Task.xml

Document Version Independent Id

6c1ba1c9-bbea-708d-1acb-992ffe03ee26

Platform Id

8a4a84a5-87ed-1449-b986-da7f74c7fb58

Article author

@dotnet-bot

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label May 25, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-threading-tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Threading.Tasks untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

1 participant