-
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
Allow using Vec::<T>::place_back for T: !Clone #40909
Conversation
The place_back was likely put into block with `T: Clone` bound by mistake.
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
My bad! |
@bors r+ |
📌 Commit 1e3bc5a has been approved by |
⌛ Testing commit 1e3bc5a with merge 47cd926... |
💔 Test failed - status-appveyor |
@bors: retry |
@bors: r+ |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 1e3bc5a has been approved by |
This PR is still reflected as failed on the queue, despite the approval or the retry. |
@bors: retry |
⌛ Testing commit 1e3bc5a with merge 495862b... |
💔 Test failed - status-travis |
The constraints per impl block are a vestige of older Rust anyway, it should be cleaned up (a single impl block for the inherent methods). |
… On Sun, Apr 2, 2017 at 8:17 PM, bluss ***@***.***> wrote:
The constraints per impl block are a vestige of older Rust anyway, it
should be cleaned up (a single impl block for the inherent methods).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#40909 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95PUAoIf1o6_bJvbD5p2NpR54pyfHks5rsFbCgaJpZM4Mtf1i>
.
|
…chton Allow using Vec::<T>::place_back for T: !Clone The place_back was likely put into block with `T: Clone` bound by mistake.
The place_back was likely put into block with
T: Clone
bound by mistake.