update rust-analyzer to 2024-01-08

[sublimelsp-app]

Update rust-analyzer from 2024-01-01 to 2024-01-08 (see all changes).

[github-actions]

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

--- /dev/fd/63	2024-01-13 10:14:31.745652762 +0000
+++ /dev/fd/62	2024-01-13 10:14:31.745652762 +0000
@@ -269,6 +269,11 @@
       "type": "string"
     }
   },
+  "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,
+    "type": "boolean"
+  },
   "rust-analyzer.cargo.buildScripts.useRustcWrapper": {
     "markdownDescription": "Use `RUSTC_WRAPPER=rust-analyzer` when running build scripts to\navoid checking unnecessary things.",
     "default": true,
@@ -414,7 +419,7 @@
     "uniqueItems": true
   },
   "rust-analyzer.check.invocationLocation": {
-    "markdownDescription": "Specifies the working directory for running checks.\n- \"workspace\": run checks for workspaces in the corresponding workspaces' root directories.\n    This falls back to \"root\" if `#rust-analyzer.cargo.check.invocationStrategy#` is set to `once`.\n- \"root\": run checks in the project's root directory.\nThis config only has an effect when `#rust-analyzer.cargo.check.overrideCommand#`\nis set.",
+    "markdownDescription": "Specifies the working directory for running checks.\n- \"workspace\": run checks for workspaces in the corresponding workspaces' root directories.\n    This falls back to \"root\" if `#rust-analyzer.check.invocationStrategy#` is set to `once`.\n- \"root\": run checks in the project's root directory.\nThis config only has an effect when `#rust-analyzer.check.overrideCommand#`\nis set.",
     "default": "workspace",
     "type": "string",
     "enum": [
@@ -427,7 +432,7 @@
     ]
   },
   "rust-analyzer.check.invocationStrategy": {
-    "markdownDescription": "Specifies the invocation strategy to use when running the check command.\nIf `per_workspace` is set, the command will be executed for each workspace.\nIf `once` is set, the command will be executed once.\nThis config only has an effect when `#rust-analyzer.cargo.check.overrideCommand#`\nis set.",
+    "markdownDescription": "Specifies the invocation strategy to use when running the check command.\nIf `per_workspace` is set, the command will be executed for each workspace.\nIf `once` is set, the command will be executed once.\nThis config only has an effect when `#rust-analyzer.check.overrideCommand#`\nis set.",
     "default": "per_workspace",
     "type": "string",
     "enum": [
@@ -448,7 +453,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.cargo.check.invocationStrategy#` and\n`#rust-analyzer.cargo.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\nAn example command would be:\n\n```bash\ncargo check --workspace --message-format=json --all-targets\n```\n.",
     "default": null,
     "type": [
       "null",
@@ -986,6 +991,11 @@
     "default": true,
     "type": "boolean"
   },
+  "rust-analyzer.inlayHints.rangeExclusiveHints.enable": {
+    "markdownDescription": "Whether to show exclusive range inlay hints.",
+    "default": false,
+    "type": "boolean"
+  },
   "rust-analyzer.inlayHints.reborrowHints.enable": {
     "markdownDescription": "Whether to show inlay hints for compiler inserted reborrows.\nThis setting is deprecated in favor of #rust-analyzer.inlayHints.expressionAdjustmentHints.enable#.",
     "default": "never",

[predragnikolic]

Hahahaha
I assume that the PR notbot(autocorrect) can be improved to not force push changes

I will force push my changes later.

[rchl]

You have to be quick. :)

But seriously, I guess the logic should be more sophisticated but not sure how it should work exactly. Maybe similarly to Renovate it should skip updating PR if it has some commits made by someone else than github or the bot itself.