-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Merge backport branches into master #4109
Conversation
…ntation Enable rustup clippy to refer to the correct documentation
[Martins Polakovs, John Firebaugh]
… level between closure parameter and "self"
As reported in rust-lang#3841. Only fixes the part where it triggers on the `derive`.
Backport some things to stable
rust-lang#4101 Splits up redundant_closure's method checking into a pedantic lint
Backport rust-lang#4101 to beta This lint has been causing lots of problems. I'll check up on other potential beta backports when I build the new changelog r? @oli-obk
Hopefully travis passes now. |
It looks like this is also hitting #4108 :/ (I won't have time to investigate until Monday) |
Ah. No rush. |
I am seeing this failure locally, too. I'll have a look |
📌 Commit 9ba60b8 has been approved by |
Merge backport branches into master Attempt 2 at #4103 This does nothing to the code, however it keeps the backport branches in master history, so that deleting a branch won't accidentally break old rustc builds
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 9ba60b8 has been approved by |
Merge backport branches into master Attempt 2 at #4103 This does nothing to the code, however it keeps the backport branches in master history, so that deleting a branch won't accidentally break old rustc builds
☀️ Test successful - checks-travis, status-appveyor |
Attempt 2 at #4103
This does nothing to the code, however it keeps the backport branches in master history, so that deleting a branch won't accidentally break old rustc builds