-
-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Connection::close docs for new API #1924
Conversation
1e4026e
to
f457890
Compare
Any comments on the updated text in the PR? Is this the right track, does it need further tweaking? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall! Some editorial nits, and I think you forgot to rework the Connection
docs after our discussion.
Could you be more specific? I did add a paragraph under |
Just the stuff you fixed in your latest commit. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for working through this with us! I think this will be a big help to clarify good patterns for users going forwards, and save us all time in explaining the subtleties.
The existing docs were no longer correct and also the suggested approach is still error prone. This describes the intricasies of closing a QUIC connection a bit more.
25fc06f
to
417cc7c
Compare
squashed into a single commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking great, thanks for all the efforts!
In the new API the finish call no longer returns a future and to achieve the same behaviour the future from stopped needs to be used.