-
Notifications
You must be signed in to change notification settings - Fork 154
Document Join APIs that may propagate exceptions #1332
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me, only minor comment
| /// </summary> | ||
| /// <returns>A task that completes when this collection is empty.</returns> | ||
| /// <remarks> | ||
| /// Any exceptions thrown by the tasks in this collection are <em>not</em> propagated to the returned task. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder it should be 'Any exception' instead of 'Any exceptions'
| /// <param name="cancellationToken">A cancellation token.</param> | ||
| /// <returns>A task that completes when this collection is empty, or is canceled when <paramref name="cancellationToken"/> is canceled.</returns> | ||
| /// <remarks> | ||
| /// Any exceptions thrown by the tasks in this collection are <em>not</em> propagated to the returned task. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the same as the previous comment.
No description provided.