[r+] TRPL: Anti-example failing for the wrong reason. #21141
Merged
Conversation
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
Really small correction. This anti-example in the Closures section is supposed to fail because of a borrow, but it was failing at the type inference because of insufficient type information. This makes it fail for the expected reason.
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see CONTRIBUTING.md for more information. |
nikomatsakis
changed the title
|
Ooops! Thanks! |
bors
added a commit
that referenced
this pull request
Jan 14, 2015
[r+] TRPL: Anti-example failing for the wrong reason. Reviewed-by: nikomatsakis
bors
referenced
this pull request
Jan 14, 2015
bors
referenced
this pull request
Jan 15, 2015
bors
added a commit
that referenced
this pull request
Jan 15, 2015
[r+] TRPL: Anti-example failing for the wrong reason. Reviewed-by: nikomatsakis
bors
added a commit
that referenced
this pull request
Jan 15, 2015
[r+] TRPL: Anti-example failing for the wrong reason. Reviewed-by: nikomatsakis
alexcrichton
added a commit
to alexcrichton/rust
that referenced
this pull request
Jan 15, 2015
Really small correction. This anti-example in the Closures section is supposed to fail because of a borrow, but it was failing at the type inference because of insufficient type information. This makes it fail for the expected reason.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Really small correction.
This anti-example in the Closures section is supposed to fail because of a borrow, but it was failing at the type inference because of insufficient type information.
This makes it fail for the expected reason.