From 50a9508f4f8a3b6d83e81ef85de568b8fbecf5e6 Mon Sep 17 00:00:00 2001
From: John Spray <john@neon.tech>
Date: Thu, 10 Aug 2023 14:38:52 +0100
Subject: [PATCH] clippy

---
 pageserver/src/deletion_queue.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pageserver/src/deletion_queue.rs b/pageserver/src/deletion_queue.rs
index ef59c9c4a3..573677943d 100644
--- a/pageserver/src/deletion_queue.rs
+++ b/pageserver/src/deletion_queue.rs
@@ -80,7 +80,7 @@ struct FlushOp {
 
 impl FlushOp {
     fn fire(self) {
-        if let Err(_) = self.tx.send(()) {
+        if self.tx.send(()).is_err() {
             // oneshot channel closed. This is legal: a client could be destroyed while waiting for a flush.
             debug!("deletion queue flush from dropped client");
         };
@@ -145,7 +145,7 @@ impl DeletionQueueClient {
 
     async fn do_flush(&self, msg: FrontendQueueMessage, rx: tokio::sync::oneshot::Receiver<()>) {
         self.do_push(msg).await;
-        if let Err(_) = rx.await {
+        if rx.await.is_err() {
             // This shouldn't happen if tenants are shut down before deletion queue.  If we
             // encounter a bug like this, then a flusher will incorrectly believe it has flushed
             // when it hasn't, possibly leading to leaking objects.