Jonathan Wakely

Search returns wrong result

2

Entering the name of a package in the search box jumps to the package and then skips on to the next one, with no way to go back to the...

[async.dispatch] uses DEDUCED without completion signatures

2

[[async.reqmts.async.return.type]](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0112r0.html#async.reqmts.async.return.type) defines DEDUCED as a type that depends on `Signature`, but then [[async.dispatch]](http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0112r0.html#async.dispatch) doesn't specify a completion signature for the dispatch/post/defer overloads that use DEDUCED. It can be inferred to...

Need wording about lifetime of execution contexts

5

I can't see any wording that makes it explicit that trying to submit functions (or other similar operations) to a context that has been destroyed is undefined e.g. ``` io_context...

What are the requirements for an EndpointSequence ?

1

Several functions take a template parameter of type `EndpointSequence` and imply iteration over it, but it's not clear what exactly the requirements are. Presumably the only requirement is for begin()...

Wording for various cancel() functions is not clear that they don't block

1

i.e. the outstanding operations should be completed asynchronously

no net::buffer() overload accepts const basic_string

3

``` const std::string s = ""; net::buffer(s); ``` This fails because the `buffer(basic_string_view)` overload cannot deduce its template arguments. We could add overloads for `string_view`, `wstring_view`, `u16string_view` and `u32string_view` but...

Overspecification? if (ec) throw system_error(ec, __func__);

3

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0112r0.html#err.report.sync says ``` error_code ec; f(a1, a2, ..., aN, ec); if (ec) throw system_error(ec, __func__); ``` It's not clear to me that using a different string to `__func__` would be...

send_to and async_send_to use inconsistent variable names

1

At http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0112r0.html#socket.dgram.op the specifications of send_to and async_send_to alternate between calling the endpoint "destination", "recipient" and (in the Effects) "sender".

Unclear lifetimes of executor work guards

1

There seems to be no difference between the lifetime of `work1` and `work2` as described by [[async.reqmts.async.work]](http://wg21.link/p0112r0#async.reqmts.async.work) [[async.reqmts.async.concepts]](http://wg21.link/p0112r0#async.reqmts.async.concepts) suggests that _"until the asynchronous operation has completed"_ and _"until the asynchronous...

basic_socket_acceptor::accept return clause unclear

1

> Returns: If `h` is an open native socket, `socket_type(ctx, s)`; otherwise `socket_type(ctx)`. What is `s`? Should it be `socket_type(ctx, protocl_, h)` ? The problem appears twice, in ``` socket_type...