fix instances of bugprone-move-forwarding-reference
Unless it's guaranteed that `std::forward` always turns into an rvalue ref, using `std::move(x)`, where `x`'s type is a universal reference, is generally unsafe. `std::forward` is preferred for these cases. The fix to the not-copy_constructible definition is... I assume a nop, but it doesn't seem harmful to change it anyway? Bug: 1134310 Change-Id: I6a40c714c6f9e393a984665c1a82e198d7a8fbcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2443403Reviewed-by:danakj <danakj@chromium.org> Commit-Queue: George Burgess <gbiv@chromium.org> Cr-Commit-Position: refs/heads/master@{#813222}
Showing
Please register or sign in to comment