Open
Conversation
Author
|
I also suggest updating the url. The previous one returned 301 permanent redirect, so a user doesn't actually see the upgrade which is the point of the example. Before: After: |
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
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.
This example failed. Looking at the code there's never any "excess", as the channel type is
socketready = Channel{Tuple{IO, Response}}(0).At first I thought this was just an outdated example, what confuses me is that from git blame I can't tell why someone thought there was an excess. Maybe it's just a mistake, as opposed to being out of date, or maybe I'm missing something.
Please review.