Lines Matching refs:executor

14 Just as with executors under the Networking TS model, a standard executor
39 implementation determines at compile time which model a particular executor
40 meets; the proposed standard executor model is used in preference if both are
49 default runtime-polymorphic executor for all I/O objects. This type alias
55 wrapper, [link boost_asio.reference.executor `executor`]. If required for backward
57 the `any_io_executor` type alias to instead point to the `executor` polymorphic
62 Standard executor properties make what were previously hard requirements on an
63 executor (such as work counting, or the ability to distinguish between `post`,
65 minimal requirements for an I/O executor are:
68   `executor`] concept.
79 The following example shows a minimal I/O executor. Given a queue submission
87 the executor may be defined as follows:
114     // This executor always has blocking.never semantics.
126 This executor may be created as follows:
131 minimal_io_executor executor{&context, queue};
137 boost::asio::ip::tcp::acceptor acceptor(executor);
144 boost::asio::any_io_executor poly_executor = executor;
150 an executor implementation conforms to the `executor` concept and type
213 executor functionality on older C++ standards. These traits may be found under