Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update rust-analyzer to 2024-01-08 #112

Merged
merged 3 commits into from
Jan 13, 2024
Merged

update rust-analyzer to 2024-01-08 #112

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
501616e
update rust-analyzer to 2024-01-08
rchl Jan 9, 2024
1ce977d
update settings
predragnikolic Jan 12, 2024
5ebc273
bring back newlines
predragnikolic Jan 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions LSP-rust-analyzer.sublime-settings
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,9 @@
// ```
// .
"rust-analyzer.cargo.buildScripts.overrideCommand": null,
// Rerun proc-macros building/build-scripts running when proc-macro
// or build-script sources change and are saved.
"rust-analyzer.cargo.buildScripts.rebuildOnSave": false,
// Use `RUSTC_WRAPPER=rust-analyzer` when running build scripts to
// avoid checking unnecessary things.
"rust-analyzer.cargo.buildScripts.useRustcWrapper": true,
Expand Down Expand Up @@ -101,14 +104,14 @@
"rust-analyzer.check.ignore": [],
// Specifies the working directory for running checks.
// - "workspace": run checks for workspaces in the corresponding workspaces' root directories.
// This falls back to "root" if `rust-analyzer.cargo.check.invocationStrategy` is set to `once`.
// This falls back to "root" if `rust-analyzer.check.invocationStrategy` is set to `once`.
// - "root": run checks in the project's root directory.
//This config only has an effect when `rust-analyzer.cargo.check.overrideCommand` is set.
// This config only has an effect when `rust-analyzer.check.overrideCommand` is set.
"rust-analyzer.check.invocationLocation": "workspace",
// Specifies the invocation strategy to use when running the check command.
// If `per_workspace` is set, the command will be executed for each workspace.
// If `once` is set, the command will be executed once.
// This config only has an effect when `rust-analyzer.cargo.check.overrideCommand` is set.
// This config only has an effect when `rust-analyzer.check.overrideCommand` is set.
"rust-analyzer.check.invocationStrategy": "per_workspace",
// Whether to pass `--no-default-features` to Cargo. Defaults to `rust-analyzer.cargo.noDefaultFeatures`.
"rust-analyzer.check.noDefaultFeatures": null,
Expand All @@ -124,8 +127,8 @@
// If there are multiple linked projects/workspaces, this command is invoked for
// each of them, with the working directory being the workspace root
// (i.e., the folder containing the `Cargo.toml`). This can be overwritten
// by changing `rust-analyzer.cargo.check.invocationStrategy` and
// `rust-analyzer.cargo.check.invocationLocation`.
// by changing `rust-analyzer.check.invocationStrategy` and
// `rust-analyzer.check.invocationLocation`.
//
// An example command would be:
//
Expand Down Expand Up @@ -324,6 +327,8 @@
"rust-analyzer.inlayHints.maxLength": 25,
// Whether to show function parameter name inlay hints at the call site.
"rust-analyzer.inlayHints.parameterHints.enable": true,
// Whether to show exclusive range inlay hints.
"rust-analyzer.inlayHints.rangeExclusiveHints.enable": false,
// Whether to show inlay type hints for compiler inserted reborrows.
// possible values: always, never, mutable
"rust-analyzer.inlayHints.reborrowHints.enable": "never",
Expand Down
2 changes: 1 addition & 1 deletion plugin.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@

SESSION_NAME = "rust-analyzer"

TAG = "2024-01-01"
TAG = "2024-01-08"
"""
Update this single git tag to download a newer version.
After changing this tag, go through the server settings again to see
Expand Down
16 changes: 13 additions & 3 deletions sublime-package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,11 @@
"array"
]
},
"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": {
"default": true,
"markdownDescription": "Use `RUSTC_WRAPPER=rust-analyzer` when running build scripts to\navoid checking unnecessary things.",
Expand Down Expand Up @@ -270,7 +275,7 @@
"Run checks in the project’s root directory.",
"Run checks for workspaces in the corresponding workspaces' root directories. This falls back to `root` if rust-analyzer.cargo.checkOnSave.invocationStrategy is set to `once`."
],
"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.",
"type": "string"
},
"rust-analyzer.check.invocationStrategy": {
Expand All @@ -283,7 +288,7 @@
"The command will be executed once.",
"The command will be executed for each workspace."
],
"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.",
"type": "string"
},
"rust-analyzer.check.noDefaultFeatures": {
Expand All @@ -295,7 +300,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,
"items": {
"type": "string"
Expand Down Expand Up @@ -888,6 +893,11 @@
"markdownDescription": "Whether to show function parameter name inlay hints at the call\nsite.",
"type": "boolean"
},
"rust-analyzer.inlayHints.rangeExclusiveHints.enable": {
"markdownDescription": "Whether to show exclusive range inlay hints.",
"default": false,
"type": "boolean"
},
"rust-analyzer.inlayHints.reborrowHints.enable": {
"default": "never",
"enum": [
Expand Down