Remove potential confusion of indexes and values with enumerate #1142
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
When encountering `enumerate()` for the first time, it's kind of confusing where all these items are coming from. The original example enumerates a list of integers. This may confuse people to think that the indexes are coming from the list, like a kind of `zip()`. If you instead use different types, this isn't possible.
carols10cents
approved these changes
Jan 31, 2018
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.
When encountering
enumerate()for the first time, it's kind of confusing where all these items are coming from. The original example enumerates a list of integers. This may confuse people to think that the indexes are coming from the list, like a kind ofzip(). If you instead use different types, this isn't possible.