en (unlikely as that is). 2, in coming up with a decent semantic approach for this annoying corner case that'll never really happen, and then thinking of how to document it, I realized the following practical truths: <code>Peer_socket::non_blocking()</code> mode affects only the non-<code>async*()</code> ops on <code>Peer_socket</code>, and it's common to want those to be non-blocking in the first place, if one also feels the need to use <code>async*()</code> (like the present function). So why jump through