Guide: Clarify that assigning/comparing different tuple types doesn't work #17836
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
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon. |
|
Thank you! Good point. |
bors
added a commit
that referenced
this pull request
Oct 8, 2014
Currently, the Guide says tuples "are only equivalent if the arity, types, and values are all identical", before presenting an example that uses `==` to compare two tuples whose arity and contained types match. This is misleading, because it implies that `==` can dynamically check whether two tuples have the same arity and contained types, whereas trying to do this would lead to a compiler error. I tried to avoid destroying the flow of this section, but I'm not sure if I've been successful.
lnicola
pushed a commit
to lnicola/rust
that referenced
this pull request
Aug 13, 2024
minor: log error when sysroot can't be discovered Closes rust-lang#17808
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.
Currently, the Guide says tuples "are only equivalent if the arity, types, and values are all identical", before presenting an example that uses
==to compare two tuples whose arity and contained types match. This is misleading, because it implies that==can dynamically check whether two tuples have the same arity and contained types, whereas trying to do this would lead to a compiler error.I tried to avoid destroying the flow of this section, but I'm not sure if I've been successful.