tmp/tmpky5qmg5m/{from.md → to.md}
RENAMED
|
@@ -0,0 +1,9 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
**Table: Types of customization point objects in the execution control library** <a id="exec.pos">[exec.pos]</a>
|
| 2 |
+
|
| 3 |
+
| Customization point object type | Purpose | Examples |
|
| 4 |
+
| ------------------------------- | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
| 5 |
+
| core | provide core execution functionality, and connection between core components | e.g., `connect`, `start` |
|
| 6 |
+
| completion functions | called by senders to announce the completion of the work (success, error, or cancellation) | `set_value`, `set_error`, `set_stopped` |
|
| 7 |
+
| senders | allow the specialization of the provided sender algorithms | sender factories (e.g., `schedule`, `just`, `read_env`); sender adaptors (e.g., `continues_on`, `then`, `let_value`); sender consumers (e.g., `sync_wait`) |
|
| 8 |
+
| queries | allow querying different properties of objects | general queries (e.g., `get_allocator`, `get_stop_token`); environment queries (e.g., `get_scheduler`, `get_delegation_scheduler`); scheduler queries (e.g., `get_forward_progress_guarantee`); sender attribute queries (e.g., `get_completion_scheduler`) |
|
| 9 |
+
|