Disconnected states must not imploy more work can be done #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Motivation: In an earlier patch for disconnect messages I accidentally missed the fact that `.noMessage` implies that more work can be done, and so is a bad return type for the disconnected states. Modifications: Disconnected states should return `nil`. Result: No infinite loops when peers go away!
artemredkin
approved these changes
Apr 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation:
In an earlier patch for disconnect messages I accidentally missed the
fact that
.noMessageimplies that more work can be done, and so is abad return type for the disconnected states.
Modifications:
Disconnected states should return
nil.Result:
No infinite loops when peers go away!