cros_async: remove ?Sized from Default bounds

Default already includes Sized, so the ?Sized is not useful.

Fixes a clippy warning in Rust 1.81.

BUG=b:365852007

Change-Id: I32a78e65153e63779cdafed4a35a542e22dd699e
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5852615
Reviewed-by: Frederick Mayle <fmayle@google.com>
Reviewed-by: Richard Zhang <rizhang@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
This commit is contained in:
Daniel Verkamp 2024-09-10 14:43:44 -07:00 committed by crosvm LUCI
parent 72550d97b1
commit a43b9346f8
2 changed files with 2 additions and 2 deletions

View file

@ -826,7 +826,7 @@ unsafe impl<T: ?Sized + Send> Send for RwLock<T> {}
#[allow(clippy::undocumented_unsafe_blocks)]
unsafe impl<T: ?Sized + Send> Sync for RwLock<T> {}
impl<T: ?Sized + Default> Default for RwLock<T> {
impl<T: Default> Default for RwLock<T> {
fn default() -> Self {
Self::new(Default::default())
}

View file

@ -100,7 +100,7 @@ unsafe impl<T: ?Sized + Send> Send for SpinLock<T> {}
#[allow(clippy::undocumented_unsafe_blocks)]
unsafe impl<T: ?Sized + Send> Sync for SpinLock<T> {}
impl<T: ?Sized + Default> Default for SpinLock<T> {
impl<T: Default> Default for SpinLock<T> {
fn default() -> Self {
Self::new(Default::default())
}