chriskohlhoff

Need to make it match what is in doc/classes/execution_context.qbk

# Changes Since P0112R0 | Commit | Kind | Issue | Description | | --- | --- | --- | --- | | c06b8aeba14d669253239efebc8451df9c41a83b | Editorial | | Fix typo...

Rather than calling the get_executor() member directly. The ExecutionContext type requirements table should be updated to use `get_associated_executor(x)` rather than `x.get_executor()`. The requirement for having a nested typedef `executor_type` should...

Associators should support non-const get_executor() members.

1

Right now this does not work: ``` class foo { typedef XYZ executor_type; executor_type get_executor() noexcept; }; foo f; get_associated_executor(f); ``` because `get_associated_executor`, and `associated_executor::get()` take the first argument by...

Consider SFINAE-enabling associators

1

Adding `class = void` to associated_allocator and associated_executor.

E.g. constructor of a service class A might perform use_service(...);

Consider whether to add char traits template parameter to basic_socket_iostream etc

4

DK thinks it would be wrong and would rather we don't go down this rabbit hole.