Closed najamelan closed 5 years ago
As far as I can tell, this warning can be fixed by just assigning that line to a variable:
let _runtime_result = runtime.block_on(runner).unwrap();
Also, I definitely second better documentation on this example, had a hard time figuring it all out. Would be happy to try and work on some documentation either after this PR is merged, or in a separate PR.
As far as i can tell, the server doesn't initiate the close handshake, so the client should just consider the handshake finished when it receives the acknowledgment and probably just wait for the server to close the underlying connection.
This stops if from trying to start a second close handshake.
It's not exactly clear to me how this avoids dropping the underlying connection before the server closes it now???
There is also a warning:
Given how convoluted types get here, I haven't exactly bothered getting to the bottom of this warning.
I think some extra comments would be nice in example code.