From cfab68d6fcad567da26630b94b0abb396fd1262e Mon Sep 17 00:00:00 2001 From: GHA CI Date: Sun, 31 Dec 2023 16:44:47 +0000 Subject: [PATCH] Automatic deploy to GitHub Pages: e1dbafd875f898a14514b39c928e735fb5a7e6b4 --- master/lints.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/master/lints.json b/master/lints.json index d2381809d790..1be495ace119 100644 --- a/master/lints.json +++ b/master/lints.json @@ -2683,7 +2683,7 @@ }, "group": "style", "level": "warn", - "docs": "\n### What it does\nChecks for usage of `x.get(0)` instead of\n`x.first()`.\n\n### Why is this bad?\nUsing `x.first()` is easier to read and has the same\nresult.\n\n### Example\n```rust\nlet x = vec![2, 3, 5];\nlet first_element = x.get(0);\n```\n\nUse instead:\n```rust\nlet x = vec![2, 3, 5];\nlet first_element = x.first();\n```", + "docs": "\n### What it does\nChecks for usage of `x.get(0)` instead of\n`x.first()` or `x.front()`.\n\n### Why is this bad?\nUsing `x.first()` for `Vec`s and slices or `x.front()`\nfor `VecDeque`s is easier to read and has the same result.\n\n### Example\n```rust\nlet x = vec![2, 3, 5];\nlet first_element = x.get(0);\n```\n\nUse instead:\n```rust\nlet x = vec![2, 3, 5];\nlet first_element = x.first();\n```", "version": "1.63.0", "applicability": { "is_multi_part_suggestion": false,