Skip to content

Commit d6ae7fb

Browse files
committed
Clarify the way in which task types are unspecified
1 parent dc4f854 commit d6ae7fb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

standard/classes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5329,7 +5329,7 @@ The *return_type* of an async method shall be either `void` or a ***task type***
53295329
53305330
An async method returning a task type is said to be ***task-returning***.
53315331
5332-
The exact definition of the task types is implementation-defined, but from the languages point of view, a task type is in one of the states *incomplete*, *succeeded* or *faulted*. A *faulted* task records a pertinent exception. A *succeeded*TaskType»<T>` records a result of type `T`. Task types are awaitable, and tasks can therefore be the operands of await expressions ([§12.9.8](expressions.md#1298-await-expressions)).
5332+
Task types can vary in their exact definition, but from the languages point of view, a task type is in one of the states *incomplete*, *succeeded* or *faulted*. A *faulted* task records a pertinent exception. A *succeeded*TaskType»<T>` records a result of type `T`. Task types are awaitable, and tasks can therefore be the operands of await expressions ([§12.9.8](expressions.md#1298-await-expressions)).
53335333
53345334
> *Example*: The task type `MyTask<T>` is associated with the task builder type `MyTaskMethodBuilder<T>` and the awaiter type `Awaiter<T>`:
53355335
>

0 commit comments

Comments
 (0)