tmp/tmpgy441_vw/{from.md → to.md}
RENAMED
|
@@ -0,0 +1,12 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
### `execution::start` <a id="exec.opstate.start">[[exec.opstate.start]]</a>
|
| 2 |
+
|
| 3 |
+
The name `start` denotes a customization point object that starts
|
| 4 |
+
[[exec.async.ops]] the asynchronous operation associated with the
|
| 5 |
+
operation state object. For a subexpression `op`, the expression
|
| 6 |
+
`start(op)` is ill-formed if `op` is an rvalue. Otherwise, it is
|
| 7 |
+
expression-equivalent to `MANDATE-NOTHROW(op.start())`.
|
| 8 |
+
|
| 9 |
+
If `op.start()` does not start [[exec.async.ops]] the asynchronous
|
| 10 |
+
operation associated with the operation state `op`, the behavior of
|
| 11 |
+
calling `start(op)` is undefined.
|
| 12 |
+
|