Expanded differentiation between tuples and parentheses evaluation #116
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
|
This doesn't seem to make it any clearer to me. |
|
I agree, withdrawn. |
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.
What threw me off is having an answer be exactly the same as the question, without needing to use my mental compiler. It wasn't until I read issue #12 and #57 when I realized that you were trying to show the difference between tuples and parentheses evaluation. I didn't realize that
(1).__class__was suppose to indicate parentheses evaluation so this pull request attempts to emphasize the difference. I feel the third example can be omitted as the two examples is sufficient.This tries to keep consistency with pull request #6 and improves in a different manner than #34