Skip to content

Increase understandability of the tuple documentation #9226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 16, 2019

Conversation

axelson
Copy link
Contributor

@axelson axelson commented Jul 16, 2019

Since Elixir data structures are immutable, emphasize that creating a new tuple is required. Also add a result binding to make it more clear that the last line is being used as a result for later.

This is based on a conversation on the forum: https://elixirforum.com/t/tuple-documentation-is-confusing-for-me/23993/3

Since Elixir data structures are immutable, emphasize that creating a new tuple
is required. Also add a `result` binding to make it more clear that the last
line is being used as a result for later.
[ci skip]
@whatyouhide whatyouhide merged commit 467496d into elixir-lang:master Jul 16, 2019
@whatyouhide
Copy link
Member

Thank you @axelson! 💟

@axelson axelson deleted the tuple-doc-update branch July 16, 2019 19:50
@axelson
Copy link
Contributor Author

axelson commented Jul 16, 2019

Thanks!

josevalim pushed a commit that referenced this pull request Jul 18, 2019
[ci skip]

Since Elixir data structures are immutable, emphasize that creating a new tuple
is required. Also add a "result" binding to make it more clear that the last
line is being used as a result for later.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants