Automatic deploy to GitHub Pages: 075996e

Author: GHA CI

master/lints.json

@@ -5393,7 +5393,7 @@
     "id": "str_to_string",
     "id_span": {
       "path": "src/strings.rs",
-      "line": 338
+      "line": 374
     },
     "group": "restriction",
     "level": "allow",
@@ -5449,7 +5449,7 @@
     "id": "string_from_utf8_as_bytes",
     "id_span": {
       "path": "src/strings.rs",
-      "line": 194
+      "line": 230
     },
     "group": "complexity",
     "level": "warn",
@@ -5473,11 +5473,25 @@
       "applicability": "MachineApplicable"
     }
   },
+  {
+    "id": "string_slice",
+    "id_span": {
+      "path": "src/strings.rs",
+      "line": 128
+    },
+    "group": "restriction",
+    "level": "allow",
+    "docs": " ### What it does\nChecks for slice operations on strings\n\n### Why is this bad?\nUTF-8 characters span multiple bytes, and it is easy to inadvertently confuse character\ncounts and string indices. This may lead to panics, and should warrant some test cases\ncontaining wide UTF-8 characters. This lint is most useful in code that should avoid\npanics at all costs.\n\n### Known problems\nProbably lots of false positives. If an index comes from a known valid position (e.g.\nobtained via `char_indices` over the same string), it is totally OK.\n\n# Example\n```rust\n&\"Ölkanne\"[1..];\n```",
+    "applicability": {
+      "is_multi_part_suggestion": false,
+      "applicability": "Unresolved"
+    }
+  },
   {
     "id": "string_to_string",
     "id_span": {
       "path": "src/strings.rs",
-      "line": 387
+      "line": 423
     },
     "group": "restriction",
     "level": "allow",