Remove unreachable err handling in setupConnection #64
Conversation
This file contains 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
If `err` is nonnil in the removed snippet, then it was also nonnil after the call to `internal.HashedTokenFromRequest` above, meaning that we would have returned before reaching the removed snippet.
kegsay
approved these changes
Apr 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If
erris nonnil in the removed snippet, then it was also nonnil after the call tointernal.HashedTokenFromRequestabove, meaning that we would have returned before reaching the removed snippet.(This shouldn't change anything at runtime, but by pruning it out I'm finding it easier to reason about what this does for #51.)