-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Rollup of 9 pull requests #33556
Merged
Merged
Rollup of 9 pull requests #33556
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
Member
steveklabnik
commented
May 11, 2016
- Successful merges: Doc improvement on std::fmt module #33129, add help on pattern guard #33260, middle: reset loop labels while visiting closure #33345, Add detailed error explanation for E0504 #33386, Inline RawVec::cap #33522, doc: Fix tiny typo in vec-alloc.md #33524, E0061 typo fix #33528, fix DFS for region error reporting #33539, Improve "since" tag placement #33542
- Failed merges: typeck: if a private field exists, also check for a public method #33342, Add detailed error explanation for E0505 #33475, Tighten span for E0063 #33517
This should fix rust-lang#31754 and follow-up rust-lang#25343. Before the latter, the closure was visited twice in the context of the enclosing fn, which made even a single closure with a loop label emit a warning. With this change, the closure is still visited within the context of the main fn (which is intended, since it is not a separate item) but resets the found loop labels while being visited. Fixes: rust-lang#31754
fix too long column fix typo of help on pattern guard one nit fix compile fail
Removed unnecessary use of threads from E0504 Cleaned up line ending on E0504 Added more examples for E0504 Changed to erroneous code wording Switched Rc example to thread/Arc example Added comments describing why errors no longer occur
Change `fast an loose` to `fast and loose`.
This was causing terrible error reports, because the algorithm was incorrectly identifying the constraints.
Doc improvement on std::fmt module Part of rust-lang#29355. r? @steveklabnik
…illaumegomez add help on pattern guard
middle: reset loop labels while visiting closure This should fix rust-lang#31754 and follow-up rust-lang#25343. Before the latter, the closure was visited twice in the context of the enclosing fn, which made even a single closure with a loop label emit a warning. With this change, the closure is still visited within the context of the main fn (which is intended, since it is not a separate item) but resets the found loop labels while being visited. Fixes: rust-lang#31754 Note: I amended the test file from rust-lang#25343, but I don't know if the original or amended test are effective, since as far as I could see, compiletest's run-pass tests do not check for zero warnings emitted? /cc @Manishearth
Add detailed error explanation for E0504 Part of rust-lang#32777
Inline RawVec::cap This was showing up in a Servo profile.
…d-loose, r=steveklabnik doc: Fix tiny typo in vec-alloc.md Change `fast an loose` to `fast and loose`.
E0061 typo fix Fixed silly typo.
fix DFS for region error reporting This was causing terrible error reports, because the algorithm was incorrectly identifying the constraints. r? @eddyb
…labnik Improve "since" tag placement Continuation of rust-lang#33431. r? @steveklabnik
r? @jroesch (rust_highfive has picked a reviewer for you, use r? to override) |
@bors: r+ p=1 |
📌 Commit 403970f has been approved by |
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.