update rust-analyzer to 2024-10-07

[sublimelsp-app[bot]]

Update rust-analyzer from 2024-09-16 to 2024-10-07 (see all changes).

[github-actions[bot]]

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

--- /dev/fd/63  2024-10-11 22:22:46.711015966 +0000
+++ /dev/fd/62  2024-10-11 22:22:46.711015966 +0000
@@ -189,6 +189,11 @@
         "type": "boolean",
         "default": false
       },
+      "rust-analyzer.debug.buildBeforeRestart": {
+        "markdownDescription": "Whether to rebuild the project modules before debugging the same test again",
+        "type": "boolean",
+        "default": false
+      },
       "rust-analyzer.debug.engineSettings": {
         "type": "object",
         "default": {},
@@ -525,6 +530,16 @@
       }
     }
   },
+  {
+    "title": "cfg",
+    "properties": {
+      "rust-analyzer.cfg.setTest": {
+        "markdownDescription": "Set `cfg(test)` for local crates. Defaults to true.",
+        "default": true,
+        "type": "boolean"
+      }
+    }
+  },
   {
     "title": "general",
     "properties": {

[rchl]

@predragnikolic the schema changes also show rust-analyzer.cfg.setTest being added

[predragnikolic]

Thanks @rchl, pushed https://github.com/sublimelsp/LSP-rust-analyzer/commit/f711aaedf79c687aedfaf65eff61424f2c42869f

I've not included the setting because I thought it was a menu item configuration in VS Code.

+  {
+    "title": "cfg",
+    "properties": {
+      "rust-analyzer.cfg.setTest": {
+        "markdownDescription": "Set `cfg(test)` for local crates. Defaults to true.",
+        "default": true,
+        "type": "boolean"
+      }
+    }
+  },

I was wrong.

[predragnikolic]

I pushed a new TAG release https://github.com/sublimelsp/LSP-rust-analyzer/releases/tag/v1.11.3