update rust-analyzer to 2024-02-26

[sublimelsp-app[bot]]

Update rust-analyzer from 2024-02-05 to 2024-02-26 (see all changes).

[github-actions[bot]]

Following are the settings schema changes between tags 2024-02-05 and 2024-02-26. Make sure that those are reflected in LSP-rust-analyzer.sublime-settings and sublime-package.json files.

--- /dev/fd/63  2024-02-26 07:52:20.929557080 +0000
+++ /dev/fd/62  2024-02-26 07:52:20.929557080 +0000
@@ -271,7 +271,7 @@
   },
   "rust-analyzer.cargo.buildScripts.rebuildOnSave": {
     "markdownDescription": "Rerun proc-macros building/build-scripts running when proc-macro\nor build-script sources change and are saved.",
-    "default": false,
+    "default": true,
     "type": "boolean"
   },
   "rust-analyzer.cargo.buildScripts.useRustcWrapper": {
@@ -458,7 +458,7 @@
     ]
   },
   "rust-analyzer.check.overrideCommand": {
-    "markdownDescription": "Override the command rust-analyzer uses instead of `cargo check` for\ndiagnostics on save. The command is required to output json and\nshould therefore include `--message-format=json` or a similar option\n(if your client supports the `colorDiagnosticOutput` experimental\ncapability, you can use `--message-format=json-diagnostic-rendered-ansi`).\n\nIf you're changing this because you're using some tool wrapping\nCargo, you might also want to change\n`#rust-analyzer.cargo.buildScripts.overrideCommand#`.\n\nIf there are multiple linked projects/workspaces, this command is invoked for\neach of them, with the working directory being the workspace root\n(i.e., the folder containing the `Cargo.toml`). This can be overwritten\nby changing `#rust-analyzer.check.invocationStrategy#` and\n`#rust-analyzer.check.invocationLocation#`.\n\nAn example command would be:\n\n```bash\ncargo check --workspace --message-format=json --all-targets\n```\n.",
+    "markdownDescription": "Override the command rust-analyzer uses instead of `cargo check` for\ndiagnostics on save. The command is required to output json and\nshould therefore include `--message-format=json` or a similar option\n(if your client supports the `colorDiagnosticOutput` experimental\ncapability, you can use `--message-format=json-diagnostic-rendered-ansi`).\n\nIf you're changing this because you're using some tool wrapping\nCargo, you might also want to change\n`#rust-analyzer.cargo.buildScripts.overrideCommand#`.\n\nIf there are multiple linked projects/workspaces, this command is invoked for\neach of them, with the working directory being the workspace root\n(i.e., the folder containing the `Cargo.toml`). This can be overwritten\nby changing `#rust-analyzer.check.invocationStrategy#` and\n`#rust-analyzer.check.invocationLocation#`.\n\nIf `$saved_file` is part of the command, rust-analyzer will pass\nthe absolute path of the saved file to the provided command. This is\nintended to be used with non-Cargo build systems.\nNote that `$saved_file` is experimental and may be removed in the futureg.\n\nAn example command would be:\n\n```bash\ncargo check --workspace --message-format=json --all-targets\n```\n.",
     "default": null,
     "type": [
       "null",
@@ -486,6 +486,11 @@
       }
     ]
   },
+  "rust-analyzer.check.workspace": {
+    "markdownDescription": "Whether `--workspace` should be passed to `cargo check`.\nIf false, `-p <package>` will be passed instead.",
+    "default": true,
+    "type": "boolean"
+  },
   "rust-analyzer.completion.autoimport.enable": {
     "markdownDescription": "Toggles the additional completions that automatically add imports when completed.\nNote that your client must specify the `additionalTextEdits` LSP client capability to truly have this feature enabled.",
     "default": true,
@@ -580,6 +585,11 @@
     },
     "type": "object"
   },
+  "rust-analyzer.completion.termSearch.enable": {
+    "markdownDescription": "Whether to enable term search based snippets like `Some(foo.bar().baz())`.",
+    "default": false,
+    "type": "boolean"
+  },
   "rust-analyzer.diagnostics.disabled": {
     "markdownDescription": "List of rust-analyzer diagnostics to disable.",
     "default": [],
@@ -1151,6 +1161,11 @@
     "default": true,
     "type": "boolean"
   },
+  "rust-analyzer.notifications.unindexedProject": {
+    "markdownDescription": "Whether to send an UnindexedProject notification to the client.",
+    "default": false,
+    "type": "boolean"
+  },
   "rust-analyzer.numThreads": {
     "markdownDescription": "How many worker threads in the main loop. The default `null` means to pick automatically.",
     "default": null,
@@ -1193,11 +1208,6 @@
     "default": false,
     "type": "boolean"
   },
-  "rust-analyzer.rename.allowExternalItems": {
-    "markdownDescription": "Allow renaming of items not belonging to the loaded workspaces.",
-    "default": false,
-    "type": "boolean"
-  },
   "rust-analyzer.runnables.command": {
     "markdownDescription": "Command to be executed instead of 'cargo' for runnables.",
     "default": null,