You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that <TcpStream as Write>::poll_closecalls<&TcpStream as Write>::poll_close which is a no-op. Would it not be more appropriate to shutdown the write direction of the socket, i.e. call TcpStream::shutdown with std::net::Shutdown::Write? Otherwise two processes that wait on each others EOF will wait forever.
The text was updated successfully, but these errors were encountered:
It seems that
<TcpStream as Write>::poll_close
calls<&TcpStream as Write>::poll_close
which is a no-op. Would it not be more appropriate to shutdown the write direction of the socket, i.e. callTcpStream::shutdown
withstd::net::Shutdown::Write
? Otherwise two processes that wait on each others EOF will wait forever.The text was updated successfully, but these errors were encountered: