-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
fixed some clippy warnings in libcollections #40541
Conversation
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
📌 Commit 70deac1 has been approved by |
☔ The latest upstream changes (presumably #40538) made this pull request unmergeable. Please resolve the merge conflicts. |
☔ The latest upstream changes (presumably #40806) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r+ |
📌 Commit 1cbfdf4 has been approved by |
@bors r- |
@bors r=brson |
📌 Commit 1cbfdf4 has been approved by |
⌛ Testing commit 1cbfdf4 with merge d05de67... |
💔 Test failed - status-appveyor |
@bors: retry
|
⌛ Testing commit 1cbfdf4 with merge 11deb59... |
💔 Test failed - status-appveyor |
@bors retry |
⌛ Testing commit 1cbfdf4 with merge 7ebc15a... |
💔 Test failed - status-appveyor |
@bors retry |
1 similar comment
@bors retry |
⌛ Testing commit 1cbfdf4 with merge 66267b3... |
💔 Test failed - status-appveyor |
… On Wed, Apr 5, 2017 at 9:29 AM, bors ***@***.***> wrote:
💔 Test failed - status-appveyor
<https://ci.appveyor.com/project/rust-lang/rust/build/1.0.2776>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#40541 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95A9lmxdalrbNADvmAghwbR-5q7Vlks5rs7NGgaJpZM4MdiL9>
.
|
@bors: r- er, hang on |
This PR is always failing with #40906, which makes me think it's not a spurious error. Turns out that's not happening on any other PRs as well. Even if this is just a bug in the MinGW linker, I don't think we can land this PR as-is. |
Scouring through, I can't find anything suspicious in the diff. |
I think I may want to bisect this. Pity that travis doesn't show the error. Hang on... |
Something hiding behind the merge in this branch? |
I'm closing this in favor of a series of smaller PRs. |
Some markdown fixes, a few readability improvements, but mostly trivial stuff.