AuroraMiddleware/asio
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Clarify impact of any_io_executor change.

Browse Source
This commit is contained in:
Christopher Kohlhoff 2020-08-05 10:04:18 +10:00
parent 331d28d98a
commit 0418d12c04
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
asio/src/doc/history.qbk
View File

@ -28,13 +28,14 @@
time which model a particular executor meets; the proposed standard
executor model is used in preference if both are detected.
* The `any_io_executor` type alias has been introduced as the default
* The `any_io_executor` type alias has been introduced as the new default
runtime-polymorphic executor for all I/O objects. This type alias points to
the `execution::any_executor<>` template with a set of supportable
properties specified for use with I/O. If required for backward
compatibility, `ASIO_USE_TS_EXECUTOR_AS_DEFAULT` can be defined, which
changes the `any_io_executor` type alias to point to the old polymorphic
wrapper, `executor`.
properties specified for use with I/O. This change may break existing code
that directly uses the old polymorphic wrapper, `executor`. If required for
backward compatibility, `ASIO_USE_TS_EXECUTOR_AS_DEFAULT` can be defined,
which changes the `any_io_executor` type alias to instead point to the
`executor` polymorphic wrapper.
* Support for the existing Networking TS model of executors can be disabled
by defining `ASIO_NO_TS_EXECUTORS`.