Update global_&_return.rst - #95
Merged
Merged
Conversation
Removed detail stating "return a,b" is not a tuple
Owner
|
Thanks |
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.
When explaining multiple return values, it shows returning a tuple in a function, and then says you can "return separate values as well as well". However, returning "separate values" is just a different way syntactically of returning a tuple. To state that they are different would be inaccurate
This can be seen even outside of functions:
I'm debating whether I should keep
name, age = profile()in, as it shows a good example of unpacking the results of a function, though unpacking itself isn't a specific function feature