Create proposal to change IteratorType post-nil guarantee #213
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
| - Not having the post-`nil` guarantee can sometimes add storage and performance | ||
| burden for the caller instead, e.g. when an iterator somehow buffers it's | ||
| underlying iterator. This in contrast can usually not be optimized away. For | ||
| example, the standard library's UTF8/UTF16 decoding has 4 instead of 3 branches |
Contributor
There was a problem hiding this comment.
Probably nitpicking, but UTF-8 and UTF-16 are spelled with a dash.
gribozavr
added a commit
that referenced
this pull request
Mar 18, 2016
Create proposal to change IteratorType post-nil guarantee
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.
No description provided.