From 648e7726cf2df8c14077e37313bef716c0bb9ef3 Mon Sep 17 00:00:00 2001
From: GHA CI <gha@ci.invalid>
Date: Wed, 11 Sep 2024 10:15:57 +0000
Subject: [PATCH] Automatic deploy to GitHub Pages:
 78bdd4508d1738e9e4f508a116af9ccf33edbdd4

---
 master/lints.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/master/lints.json b/master/lints.json
index d15699c8772a..867b26aad5a1 100644
--- a/master/lints.json
+++ b/master/lints.json
@@ -6637,7 +6637,7 @@
     "id_location": "clippy_lints/src/loops/mod.rs#L210",
     "group": "complexity",
     "level": "warn",
-    "docs": "### What it does\nDetects `loop + match` combinations that are easier\nwritten as a `while let` loop.\n\n### Why is this bad?\nThe `while let` loop is usually shorter and more\nreadable.\n\n### Known problems\nSometimes the wrong binding is displayed ([#383](https://github.com/rust-lang/rust-clippy/issues/383)).\n\n### Example\n```rust\nloop {\n    let x = match y {\n        Some(x) => x,\n        None => break,\n    };\n    // .. do something with x\n}\n// is easier written as\nwhile let Some(x) = y {\n    // .. do something with x\n};\n```\n",
+    "docs": "### What it does\nDetects `loop + match` combinations that are easier\nwritten as a `while let` loop.\n\n### Why is this bad?\nThe `while let` loop is usually shorter and more\nreadable.\n\n### Example\n```rust\nlet y = Some(1);\nloop {\n    let x = match y {\n        Some(x) => x,\n        None => break,\n    };\n    // ..\n}\n```\nUse instead:\n```rust\nlet y = Some(1);\nwhile let Some(x) = y {\n    // ..\n};\n```\n",
     "version": "pre 1.29.0",
     "applicability": "HasPlaceholders"
   },