fork/rust
git clone https://git.julia.blue/fork/rust
3bcad65fbf6
master
1[[rust-analyzer.assist.emitMustUse]]rust-analyzer.assist.emitMustUse (default: `false`):: 2+ 3-- 4Whether to insert #[must_use] when generating `as_` methods 5for enum variants. 6-- 7[[rust-analyzer.assist.expressionFillDefault]]rust-analyzer.assist.expressionFillDefault (default: `"todo"`):: 8+ 9-- 10Placeholder expression to use for missing expressions in assists. 11-- 12[[rust-analyzer.cachePriming.enable]]rust-analyzer.cachePriming.enable (default: `true`):: 13+ 14-- 15Warm up caches on project load. 16-- 17[[rust-analyzer.cachePriming.numThreads]]rust-analyzer.cachePriming.numThreads (default: `0`):: 18+ 19-- 20How many worker threads to handle priming caches. The default `0` means to pick automatically. 21-- 22[[rust-analyzer.cargo.autoreload]]rust-analyzer.cargo.autoreload (default: `true`):: 23+ 24-- 25Automatically refresh project info via `cargo metadata` on 26`Cargo.toml` or `.cargo/config.toml` changes. 27-- 28[[rust-analyzer.cargo.buildScripts.enable]]rust-analyzer.cargo.buildScripts.enable (default: `true`):: 29+ 30-- 31Run build scripts (`build.rs`) for more precise code analysis. 32-- 33[[rust-analyzer.cargo.buildScripts.invocationLocation]]rust-analyzer.cargo.buildScripts.invocationLocation (default: `"workspace"`):: 34+ 35-- 36Specifies the working directory for running build scripts. 37- "workspace": run build scripts for a workspace in the workspace's root directory. 38 This is incompatible with `#rust-analyzer.cargo.buildScripts.invocationStrategy#` set to `once`. 39- "root": run build scripts in the project's root directory. 40This config only has an effect when `#rust-analyzer.cargo.buildScripts.overrideCommand#` 41is set. 42-- 43[[rust-analyzer.cargo.buildScripts.invocationStrategy]]rust-analyzer.cargo.buildScripts.invocationStrategy (default: `"per_workspace"`):: 44+ 45-- 46Specifies the invocation strategy to use when running the build scripts command. 47If `per_workspace` is set, the command will be executed for each workspace. 48If `once` is set, the command will be executed once. 49This config only has an effect when `#rust-analyzer.cargo.buildScripts.overrideCommand#` 50is set. 51-- 52[[rust-analyzer.cargo.buildScripts.overrideCommand]]rust-analyzer.cargo.buildScripts.overrideCommand (default: `null`):: 53+ 54-- 55Override the command rust-analyzer uses to run build scripts and 56build procedural macros. The command is required to output json 57and should therefore include `--message-format=json` or a similar 58option. 59 60By default, a cargo invocation will be constructed for the configured 61targets and features, with the following base command line: 62 63```bash 64cargo check --quiet --workspace --message-format=json --all-targets 65``` 66. 67-- 68[[rust-analyzer.cargo.buildScripts.useRustcWrapper]]rust-analyzer.cargo.buildScripts.useRustcWrapper (default: `true`):: 69+ 70-- 71Use `RUSTC_WRAPPER=rust-analyzer` when running build scripts to 72avoid checking unnecessary things. 73-- 74[[rust-analyzer.cargo.cfgs]]rust-analyzer.cargo.cfgs (default: `{}`):: 75+ 76-- 77List of cfg options to enable with the given values. 78-- 79[[rust-analyzer.cargo.extraArgs]]rust-analyzer.cargo.extraArgs (default: `[]`):: 80+ 81-- 82Extra arguments that are passed to every cargo invocation. 83-- 84[[rust-analyzer.cargo.extraEnv]]rust-analyzer.cargo.extraEnv (default: `{}`):: 85+ 86-- 87Extra environment variables that will be set when running cargo, rustc 88or other commands within the workspace. Useful for setting RUSTFLAGS. 89-- 90[[rust-analyzer.cargo.features]]rust-analyzer.cargo.features (default: `[]`):: 91+ 92-- 93List of features to activate. 94 95Set this to `"all"` to pass `--all-features` to cargo. 96-- 97[[rust-analyzer.cargo.noDefaultFeatures]]rust-analyzer.cargo.noDefaultFeatures (default: `false`):: 98+ 99-- 100Whether to pass `--no-default-features` to cargo. 101-- 102[[rust-analyzer.cargo.sysroot]]rust-analyzer.cargo.sysroot (default: `"discover"`):: 103+ 104-- 105Relative path to the sysroot, or "discover" to try to automatically find it via 106"rustc --print sysroot". 107 108Unsetting this disables sysroot loading. 109 110This option does not take effect until rust-analyzer is restarted. 111-- 112[[rust-analyzer.cargo.sysrootSrc]]rust-analyzer.cargo.sysrootSrc (default: `null`):: 113+ 114-- 115Relative path to the sysroot library sources. If left unset, this will default to 116`{cargo.sysroot}/lib/rustlib/src/rust/library`. 117 118This option does not take effect until rust-analyzer is restarted. 119-- 120[[rust-analyzer.cargo.target]]rust-analyzer.cargo.target (default: `null`):: 121+ 122-- 123Compilation target override (target triple). 124-- 125[[rust-analyzer.cargo.unsetTest]]rust-analyzer.cargo.unsetTest (default: `["core"]`):: 126+ 127-- 128Unsets the implicit `#[cfg(test)]` for the specified crates. 129-- 130[[rust-analyzer.checkOnSave]]rust-analyzer.checkOnSave (default: `true`):: 131+ 132-- 133Run the check command for diagnostics on save. 134-- 135[[rust-analyzer.check.allTargets]]rust-analyzer.check.allTargets (default: `true`):: 136+ 137-- 138Check all targets and tests (`--all-targets`). 139-- 140[[rust-analyzer.check.command]]rust-analyzer.check.command (default: `"check"`):: 141+ 142-- 143Cargo command to use for `cargo check`. 144-- 145[[rust-analyzer.check.extraArgs]]rust-analyzer.check.extraArgs (default: `[]`):: 146+ 147-- 148Extra arguments for `cargo check`. 149-- 150[[rust-analyzer.check.extraEnv]]rust-analyzer.check.extraEnv (default: `{}`):: 151+ 152-- 153Extra environment variables that will be set when running `cargo check`. 154Extends `#rust-analyzer.cargo.extraEnv#`. 155-- 156[[rust-analyzer.check.features]]rust-analyzer.check.features (default: `null`):: 157+ 158-- 159List of features to activate. Defaults to 160`#rust-analyzer.cargo.features#`. 161 162Set to `"all"` to pass `--all-features` to Cargo. 163-- 164[[rust-analyzer.check.ignore]]rust-analyzer.check.ignore (default: `[]`):: 165+ 166-- 167List of `cargo check` (or other command specified in `check.command`) diagnostics to ignore. 168 169For example for `cargo check`: `dead_code`, `unused_imports`, `unused_variables`,... 170-- 171[[rust-analyzer.check.invocationLocation]]rust-analyzer.check.invocationLocation (default: `"workspace"`):: 172+ 173-- 174Specifies the working directory for running checks. 175- "workspace": run checks for workspaces in the corresponding workspaces' root directories. 176 This falls back to "root" if `#rust-analyzer.cargo.check.invocationStrategy#` is set to `once`. 177- "root": run checks in the project's root directory. 178This config only has an effect when `#rust-analyzer.cargo.check.overrideCommand#` 179is set. 180-- 181[[rust-analyzer.check.invocationStrategy]]rust-analyzer.check.invocationStrategy (default: `"per_workspace"`):: 182+ 183-- 184Specifies the invocation strategy to use when running the check command. 185If `per_workspace` is set, the command will be executed for each workspace. 186If `once` is set, the command will be executed once. 187This config only has an effect when `#rust-analyzer.cargo.check.overrideCommand#` 188is set. 189-- 190[[rust-analyzer.check.noDefaultFeatures]]rust-analyzer.check.noDefaultFeatures (default: `null`):: 191+ 192-- 193Whether to pass `--no-default-features` to Cargo. Defaults to 194`#rust-analyzer.cargo.noDefaultFeatures#`. 195-- 196[[rust-analyzer.check.overrideCommand]]rust-analyzer.check.overrideCommand (default: `null`):: 197+ 198-- 199Override the command rust-analyzer uses instead of `cargo check` for 200diagnostics on save. The command is required to output json and 201should therefore include `--message-format=json` or a similar option 202(if your client supports the `colorDiagnosticOutput` experimental 203capability, you can use `--message-format=json-diagnostic-rendered-ansi`). 204 205If you're changing this because you're using some tool wrapping 206Cargo, you might also want to change 207`#rust-analyzer.cargo.buildScripts.overrideCommand#`. 208 209If there are multiple linked projects, this command is invoked for 210each of them, with the working directory being the project root 211(i.e., the folder containing the `Cargo.toml`). 212 213An example command would be: 214 215```bash 216cargo check --workspace --message-format=json --all-targets 217``` 218. 219-- 220[[rust-analyzer.check.targets]]rust-analyzer.check.targets (default: `null`):: 221+ 222-- 223Check for specific targets. Defaults to `#rust-analyzer.cargo.target#` if empty. 224 225Can be a single target, e.g. `"x86_64-unknown-linux-gnu"` or a list of targets, e.g. 226`["aarch64-apple-darwin", "x86_64-apple-darwin"]`. 227 228Aliased as `"checkOnSave.targets"`. 229-- 230[[rust-analyzer.completion.autoimport.enable]]rust-analyzer.completion.autoimport.enable (default: `true`):: 231+ 232-- 233Toggles the additional completions that automatically add imports when completed. 234Note that your client must specify the `additionalTextEdits` LSP client capability to truly have this feature enabled. 235-- 236[[rust-analyzer.completion.autoself.enable]]rust-analyzer.completion.autoself.enable (default: `true`):: 237+ 238-- 239Toggles the additional completions that automatically show method calls and field accesses 240with `self` prefixed to them when inside a method. 241-- 242[[rust-analyzer.completion.callable.snippets]]rust-analyzer.completion.callable.snippets (default: `"fill_arguments"`):: 243+ 244-- 245Whether to add parenthesis and argument snippets when completing function. 246-- 247[[rust-analyzer.completion.limit]]rust-analyzer.completion.limit (default: `null`):: 248+ 249-- 250Maximum number of completions to return. If `None`, the limit is infinite. 251-- 252[[rust-analyzer.completion.postfix.enable]]rust-analyzer.completion.postfix.enable (default: `true`):: 253+ 254-- 255Whether to show postfix snippets like `dbg`, `if`, `not`, etc. 256-- 257[[rust-analyzer.completion.privateEditable.enable]]rust-analyzer.completion.privateEditable.enable (default: `false`):: 258+ 259-- 260Enables completions of private items and fields that are defined in the current workspace even if they are not visible at the current position. 261-- 262[[rust-analyzer.completion.snippets.custom]]rust-analyzer.completion.snippets.custom:: 263+ 264-- 265Default: 266---- 267{ 268 "Arc::new": { 269 "postfix": "arc", 270 "body": "Arc::new(${receiver})", 271 "requires": "std::sync::Arc", 272 "description": "Put the expression into an `Arc`", 273 "scope": "expr" 274 }, 275 "Rc::new": { 276 "postfix": "rc", 277 "body": "Rc::new(${receiver})", 278 "requires": "std::rc::Rc", 279 "description": "Put the expression into an `Rc`", 280 "scope": "expr" 281 }, 282 "Box::pin": { 283 "postfix": "pinbox", 284 "body": "Box::pin(${receiver})", 285 "requires": "std::boxed::Box", 286 "description": "Put the expression into a pinned `Box`", 287 "scope": "expr" 288 }, 289 "Ok": { 290 "postfix": "ok", 291 "body": "Ok(${receiver})", 292 "description": "Wrap the expression in a `Result::Ok`", 293 "scope": "expr" 294 }, 295 "Err": { 296 "postfix": "err", 297 "body": "Err(${receiver})", 298 "description": "Wrap the expression in a `Result::Err`", 299 "scope": "expr" 300 }, 301 "Some": { 302 "postfix": "some", 303 "body": "Some(${receiver})", 304 "description": "Wrap the expression in an `Option::Some`", 305 "scope": "expr" 306 } 307 } 308---- 309Custom completion snippets. 310 311-- 312[[rust-analyzer.diagnostics.disabled]]rust-analyzer.diagnostics.disabled (default: `[]`):: 313+ 314-- 315List of rust-analyzer diagnostics to disable. 316-- 317[[rust-analyzer.diagnostics.enable]]rust-analyzer.diagnostics.enable (default: `true`):: 318+ 319-- 320Whether to show native rust-analyzer diagnostics. 321-- 322[[rust-analyzer.diagnostics.experimental.enable]]rust-analyzer.diagnostics.experimental.enable (default: `false`):: 323+ 324-- 325Whether to show experimental rust-analyzer diagnostics that might 326have more false positives than usual. 327-- 328[[rust-analyzer.diagnostics.remapPrefix]]rust-analyzer.diagnostics.remapPrefix (default: `{}`):: 329+ 330-- 331Map of prefixes to be substituted when parsing diagnostic file paths. 332This should be the reverse mapping of what is passed to `rustc` as `--remap-path-prefix`. 333-- 334[[rust-analyzer.diagnostics.warningsAsHint]]rust-analyzer.diagnostics.warningsAsHint (default: `[]`):: 335+ 336-- 337List of warnings that should be displayed with hint severity. 338 339The warnings will be indicated by faded text or three dots in code 340and will not show up in the `Problems Panel`. 341-- 342[[rust-analyzer.diagnostics.warningsAsInfo]]rust-analyzer.diagnostics.warningsAsInfo (default: `[]`):: 343+ 344-- 345List of warnings that should be displayed with info severity. 346 347The warnings will be indicated by a blue squiggly underline in code 348and a blue icon in the `Problems Panel`. 349-- 350[[rust-analyzer.files.excludeDirs]]rust-analyzer.files.excludeDirs (default: `[]`):: 351+ 352-- 353These directories will be ignored by rust-analyzer. They are 354relative to the workspace root, and globs are not supported. You may 355also need to add the folders to Code's `files.watcherExclude`. 356-- 357[[rust-analyzer.files.watcher]]rust-analyzer.files.watcher (default: `"client"`):: 358+ 359-- 360Controls file watching implementation. 361-- 362[[rust-analyzer.highlightRelated.breakPoints.enable]]rust-analyzer.highlightRelated.breakPoints.enable (default: `true`):: 363+ 364-- 365Enables highlighting of related references while the cursor is on `break`, `loop`, `while`, or `for` keywords. 366-- 367[[rust-analyzer.highlightRelated.closureCaptures.enable]]rust-analyzer.highlightRelated.closureCaptures.enable (default: `true`):: 368+ 369-- 370Enables highlighting of all captures of a closure while the cursor is on the `|` or move keyword of a closure. 371-- 372[[rust-analyzer.highlightRelated.exitPoints.enable]]rust-analyzer.highlightRelated.exitPoints.enable (default: `true`):: 373+ 374-- 375Enables highlighting of all exit points while the cursor is on any `return`, `?`, `fn`, or return type arrow (`->`). 376-- 377[[rust-analyzer.highlightRelated.references.enable]]rust-analyzer.highlightRelated.references.enable (default: `true`):: 378+ 379-- 380Enables highlighting of related references while the cursor is on any identifier. 381-- 382[[rust-analyzer.highlightRelated.yieldPoints.enable]]rust-analyzer.highlightRelated.yieldPoints.enable (default: `true`):: 383+ 384-- 385Enables highlighting of all break points for a loop or block context while the cursor is on any `async` or `await` keywords. 386-- 387[[rust-analyzer.hover.actions.debug.enable]]rust-analyzer.hover.actions.debug.enable (default: `true`):: 388+ 389-- 390Whether to show `Debug` action. Only applies when 391`#rust-analyzer.hover.actions.enable#` is set. 392-- 393[[rust-analyzer.hover.actions.enable]]rust-analyzer.hover.actions.enable (default: `true`):: 394+ 395-- 396Whether to show HoverActions in Rust files. 397-- 398[[rust-analyzer.hover.actions.gotoTypeDef.enable]]rust-analyzer.hover.actions.gotoTypeDef.enable (default: `true`):: 399+ 400-- 401Whether to show `Go to Type Definition` action. Only applies when 402`#rust-analyzer.hover.actions.enable#` is set. 403-- 404[[rust-analyzer.hover.actions.implementations.enable]]rust-analyzer.hover.actions.implementations.enable (default: `true`):: 405+ 406-- 407Whether to show `Implementations` action. Only applies when 408`#rust-analyzer.hover.actions.enable#` is set. 409-- 410[[rust-analyzer.hover.actions.references.enable]]rust-analyzer.hover.actions.references.enable (default: `false`):: 411+ 412-- 413Whether to show `References` action. Only applies when 414`#rust-analyzer.hover.actions.enable#` is set. 415-- 416[[rust-analyzer.hover.actions.run.enable]]rust-analyzer.hover.actions.run.enable (default: `true`):: 417+ 418-- 419Whether to show `Run` action. Only applies when 420`#rust-analyzer.hover.actions.enable#` is set. 421-- 422[[rust-analyzer.hover.documentation.enable]]rust-analyzer.hover.documentation.enable (default: `true`):: 423+ 424-- 425Whether to show documentation on hover. 426-- 427[[rust-analyzer.hover.documentation.keywords.enable]]rust-analyzer.hover.documentation.keywords.enable (default: `true`):: 428+ 429-- 430Whether to show keyword hover popups. Only applies when 431`#rust-analyzer.hover.documentation.enable#` is set. 432-- 433[[rust-analyzer.hover.links.enable]]rust-analyzer.hover.links.enable (default: `true`):: 434+ 435-- 436Use markdown syntax for links on hover. 437-- 438[[rust-analyzer.hover.memoryLayout.alignment]]rust-analyzer.hover.memoryLayout.alignment (default: `"hexadecimal"`):: 439+ 440-- 441How to render the align information in a memory layout hover. 442-- 443[[rust-analyzer.hover.memoryLayout.enable]]rust-analyzer.hover.memoryLayout.enable (default: `true`):: 444+ 445-- 446Whether to show memory layout data on hover. 447-- 448[[rust-analyzer.hover.memoryLayout.niches]]rust-analyzer.hover.memoryLayout.niches (default: `false`):: 449+ 450-- 451How to render the niche information in a memory layout hover. 452-- 453[[rust-analyzer.hover.memoryLayout.offset]]rust-analyzer.hover.memoryLayout.offset (default: `"hexadecimal"`):: 454+ 455-- 456How to render the offset information in a memory layout hover. 457-- 458[[rust-analyzer.hover.memoryLayout.size]]rust-analyzer.hover.memoryLayout.size (default: `"both"`):: 459+ 460-- 461How to render the size information in a memory layout hover. 462-- 463[[rust-analyzer.imports.granularity.enforce]]rust-analyzer.imports.granularity.enforce (default: `false`):: 464+ 465-- 466Whether to enforce the import granularity setting for all files. If set to false rust-analyzer will try to keep import styles consistent per file. 467-- 468[[rust-analyzer.imports.granularity.group]]rust-analyzer.imports.granularity.group (default: `"crate"`):: 469+ 470-- 471How imports should be grouped into use statements. 472-- 473[[rust-analyzer.imports.group.enable]]rust-analyzer.imports.group.enable (default: `true`):: 474+ 475-- 476Group inserted imports by the https://rust-analyzer.github.io/manual.html#auto-import[following order]. Groups are separated by newlines. 477-- 478[[rust-analyzer.imports.merge.glob]]rust-analyzer.imports.merge.glob (default: `true`):: 479+ 480-- 481Whether to allow import insertion to merge new imports into single path glob imports like `use std::fmt::*;`. 482-- 483[[rust-analyzer.imports.prefer.no.std]]rust-analyzer.imports.prefer.no.std (default: `false`):: 484+ 485-- 486Prefer to unconditionally use imports of the core and alloc crate, over the std crate. 487-- 488[[rust-analyzer.imports.prefix]]rust-analyzer.imports.prefix (default: `"plain"`):: 489+ 490-- 491The path structure for newly inserted paths to use. 492-- 493[[rust-analyzer.inlayHints.bindingModeHints.enable]]rust-analyzer.inlayHints.bindingModeHints.enable (default: `false`):: 494+ 495-- 496Whether to show inlay type hints for binding modes. 497-- 498[[rust-analyzer.inlayHints.chainingHints.enable]]rust-analyzer.inlayHints.chainingHints.enable (default: `true`):: 499+ 500-- 501Whether to show inlay type hints for method chains. 502-- 503[[rust-analyzer.inlayHints.closingBraceHints.enable]]rust-analyzer.inlayHints.closingBraceHints.enable (default: `true`):: 504+ 505-- 506Whether to show inlay hints after a closing `}` to indicate what item it belongs to. 507-- 508[[rust-analyzer.inlayHints.closingBraceHints.minLines]]rust-analyzer.inlayHints.closingBraceHints.minLines (default: `25`):: 509+ 510-- 511Minimum number of lines required before the `}` until the hint is shown (set to 0 or 1 512to always show them). 513-- 514[[rust-analyzer.inlayHints.closureCaptureHints.enable]]rust-analyzer.inlayHints.closureCaptureHints.enable (default: `false`):: 515+ 516-- 517Whether to show inlay hints for closure captures. 518-- 519[[rust-analyzer.inlayHints.closureReturnTypeHints.enable]]rust-analyzer.inlayHints.closureReturnTypeHints.enable (default: `"never"`):: 520+ 521-- 522Whether to show inlay type hints for return types of closures. 523-- 524[[rust-analyzer.inlayHints.closureStyle]]rust-analyzer.inlayHints.closureStyle (default: `"impl_fn"`):: 525+ 526-- 527Closure notation in type and chaining inlay hints. 528-- 529[[rust-analyzer.inlayHints.discriminantHints.enable]]rust-analyzer.inlayHints.discriminantHints.enable (default: `"never"`):: 530+ 531-- 532Whether to show enum variant discriminant hints. 533-- 534[[rust-analyzer.inlayHints.expressionAdjustmentHints.enable]]rust-analyzer.inlayHints.expressionAdjustmentHints.enable (default: `"never"`):: 535+ 536-- 537Whether to show inlay hints for type adjustments. 538-- 539[[rust-analyzer.inlayHints.expressionAdjustmentHints.hideOutsideUnsafe]]rust-analyzer.inlayHints.expressionAdjustmentHints.hideOutsideUnsafe (default: `false`):: 540+ 541-- 542Whether to hide inlay hints for type adjustments outside of `unsafe` blocks. 543-- 544[[rust-analyzer.inlayHints.expressionAdjustmentHints.mode]]rust-analyzer.inlayHints.expressionAdjustmentHints.mode (default: `"prefix"`):: 545+ 546-- 547Whether to show inlay hints as postfix ops (`.*` instead of `*`, etc). 548-- 549[[rust-analyzer.inlayHints.lifetimeElisionHints.enable]]rust-analyzer.inlayHints.lifetimeElisionHints.enable (default: `"never"`):: 550+ 551-- 552Whether to show inlay type hints for elided lifetimes in function signatures. 553-- 554[[rust-analyzer.inlayHints.lifetimeElisionHints.useParameterNames]]rust-analyzer.inlayHints.lifetimeElisionHints.useParameterNames (default: `false`):: 555+ 556-- 557Whether to prefer using parameter names as the name for elided lifetime hints if possible. 558-- 559[[rust-analyzer.inlayHints.maxLength]]rust-analyzer.inlayHints.maxLength (default: `25`):: 560+ 561-- 562Maximum length for inlay hints. Set to null to have an unlimited length. 563-- 564[[rust-analyzer.inlayHints.parameterHints.enable]]rust-analyzer.inlayHints.parameterHints.enable (default: `true`):: 565+ 566-- 567Whether to show function parameter name inlay hints at the call 568site. 569-- 570[[rust-analyzer.inlayHints.reborrowHints.enable]]rust-analyzer.inlayHints.reborrowHints.enable (default: `"never"`):: 571+ 572-- 573Whether to show inlay hints for compiler inserted reborrows. 574This setting is deprecated in favor of #rust-analyzer.inlayHints.expressionAdjustmentHints.enable#. 575-- 576[[rust-analyzer.inlayHints.renderColons]]rust-analyzer.inlayHints.renderColons (default: `true`):: 577+ 578-- 579Whether to render leading colons for type hints, and trailing colons for parameter hints. 580-- 581[[rust-analyzer.inlayHints.typeHints.enable]]rust-analyzer.inlayHints.typeHints.enable (default: `true`):: 582+ 583-- 584Whether to show inlay type hints for variables. 585-- 586[[rust-analyzer.inlayHints.typeHints.hideClosureInitialization]]rust-analyzer.inlayHints.typeHints.hideClosureInitialization (default: `false`):: 587+ 588-- 589Whether to hide inlay type hints for `let` statements that initialize to a closure. 590Only applies to closures with blocks, same as `#rust-analyzer.inlayHints.closureReturnTypeHints.enable#`. 591-- 592[[rust-analyzer.inlayHints.typeHints.hideNamedConstructor]]rust-analyzer.inlayHints.typeHints.hideNamedConstructor (default: `false`):: 593+ 594-- 595Whether to hide inlay type hints for constructors. 596-- 597[[rust-analyzer.interpret.tests]]rust-analyzer.interpret.tests (default: `false`):: 598+ 599-- 600Enables the experimental support for interpreting tests. 601-- 602[[rust-analyzer.joinLines.joinAssignments]]rust-analyzer.joinLines.joinAssignments (default: `true`):: 603+ 604-- 605Join lines merges consecutive declaration and initialization of an assignment. 606-- 607[[rust-analyzer.joinLines.joinElseIf]]rust-analyzer.joinLines.joinElseIf (default: `true`):: 608+ 609-- 610Join lines inserts else between consecutive ifs. 611-- 612[[rust-analyzer.joinLines.removeTrailingComma]]rust-analyzer.joinLines.removeTrailingComma (default: `true`):: 613+ 614-- 615Join lines removes trailing commas. 616-- 617[[rust-analyzer.joinLines.unwrapTrivialBlock]]rust-analyzer.joinLines.unwrapTrivialBlock (default: `true`):: 618+ 619-- 620Join lines unwraps trivial blocks. 621-- 622[[rust-analyzer.lens.debug.enable]]rust-analyzer.lens.debug.enable (default: `true`):: 623+ 624-- 625Whether to show `Debug` lens. Only applies when 626`#rust-analyzer.lens.enable#` is set. 627-- 628[[rust-analyzer.lens.enable]]rust-analyzer.lens.enable (default: `true`):: 629+ 630-- 631Whether to show CodeLens in Rust files. 632-- 633[[rust-analyzer.lens.forceCustomCommands]]rust-analyzer.lens.forceCustomCommands (default: `true`):: 634+ 635-- 636Internal config: use custom client-side commands even when the 637client doesn't set the corresponding capability. 638-- 639[[rust-analyzer.lens.implementations.enable]]rust-analyzer.lens.implementations.enable (default: `true`):: 640+ 641-- 642Whether to show `Implementations` lens. Only applies when 643`#rust-analyzer.lens.enable#` is set. 644-- 645[[rust-analyzer.lens.location]]rust-analyzer.lens.location (default: `"above_name"`):: 646+ 647-- 648Where to render annotations. 649-- 650[[rust-analyzer.lens.references.adt.enable]]rust-analyzer.lens.references.adt.enable (default: `false`):: 651+ 652-- 653Whether to show `References` lens for Struct, Enum, and Union. 654Only applies when `#rust-analyzer.lens.enable#` is set. 655-- 656[[rust-analyzer.lens.references.enumVariant.enable]]rust-analyzer.lens.references.enumVariant.enable (default: `false`):: 657+ 658-- 659Whether to show `References` lens for Enum Variants. 660Only applies when `#rust-analyzer.lens.enable#` is set. 661-- 662[[rust-analyzer.lens.references.method.enable]]rust-analyzer.lens.references.method.enable (default: `false`):: 663+ 664-- 665Whether to show `Method References` lens. Only applies when 666`#rust-analyzer.lens.enable#` is set. 667-- 668[[rust-analyzer.lens.references.trait.enable]]rust-analyzer.lens.references.trait.enable (default: `false`):: 669+ 670-- 671Whether to show `References` lens for Trait. 672Only applies when `#rust-analyzer.lens.enable#` is set. 673-- 674[[rust-analyzer.lens.run.enable]]rust-analyzer.lens.run.enable (default: `true`):: 675+ 676-- 677Whether to show `Run` lens. Only applies when 678`#rust-analyzer.lens.enable#` is set. 679-- 680[[rust-analyzer.linkedProjects]]rust-analyzer.linkedProjects (default: `[]`):: 681+ 682-- 683Disable project auto-discovery in favor of explicitly specified set 684of projects. 685 686Elements must be paths pointing to `Cargo.toml`, 687`rust-project.json`, or JSON objects in `rust-project.json` format. 688-- 689[[rust-analyzer.lru.capacity]]rust-analyzer.lru.capacity (default: `null`):: 690+ 691-- 692Number of syntax trees rust-analyzer keeps in memory. Defaults to 128. 693-- 694[[rust-analyzer.lru.query.capacities]]rust-analyzer.lru.query.capacities (default: `{}`):: 695+ 696-- 697Sets the LRU capacity of the specified queries. 698-- 699[[rust-analyzer.notifications.cargoTomlNotFound]]rust-analyzer.notifications.cargoTomlNotFound (default: `true`):: 700+ 701-- 702Whether to show `can't find Cargo.toml` error message. 703-- 704[[rust-analyzer.numThreads]]rust-analyzer.numThreads (default: `null`):: 705+ 706-- 707How many worker threads in the main loop. The default `null` means to pick automatically. 708-- 709[[rust-analyzer.procMacro.attributes.enable]]rust-analyzer.procMacro.attributes.enable (default: `true`):: 710+ 711-- 712Expand attribute macros. Requires `#rust-analyzer.procMacro.enable#` to be set. 713-- 714[[rust-analyzer.procMacro.enable]]rust-analyzer.procMacro.enable (default: `true`):: 715+ 716-- 717Enable support for procedural macros, implies `#rust-analyzer.cargo.buildScripts.enable#`. 718-- 719[[rust-analyzer.procMacro.ignored]]rust-analyzer.procMacro.ignored (default: `{}`):: 720+ 721-- 722These proc-macros will be ignored when trying to expand them. 723 724This config takes a map of crate names with the exported proc-macro names to ignore as values. 725-- 726[[rust-analyzer.procMacro.server]]rust-analyzer.procMacro.server (default: `null`):: 727+ 728-- 729Internal config, path to proc-macro server executable. 730-- 731[[rust-analyzer.references.excludeImports]]rust-analyzer.references.excludeImports (default: `false`):: 732+ 733-- 734Exclude imports from find-all-references. 735-- 736[[rust-analyzer.runnables.command]]rust-analyzer.runnables.command (default: `null`):: 737+ 738-- 739Command to be executed instead of 'cargo' for runnables. 740-- 741[[rust-analyzer.runnables.extraArgs]]rust-analyzer.runnables.extraArgs (default: `[]`):: 742+ 743-- 744Additional arguments to be passed to cargo for runnables such as 745tests or binaries. For example, it may be `--release`. 746-- 747[[rust-analyzer.rustc.source]]rust-analyzer.rustc.source (default: `null`):: 748+ 749-- 750Path to the Cargo.toml of the rust compiler workspace, for usage in rustc_private 751projects, or "discover" to try to automatically find it if the `rustc-dev` component 752is installed. 753 754Any project which uses rust-analyzer with the rustcPrivate 755crates must set `[package.metadata.rust-analyzer] rustc_private=true` to use it. 756 757This option does not take effect until rust-analyzer is restarted. 758-- 759[[rust-analyzer.rustfmt.extraArgs]]rust-analyzer.rustfmt.extraArgs (default: `[]`):: 760+ 761-- 762Additional arguments to `rustfmt`. 763-- 764[[rust-analyzer.rustfmt.overrideCommand]]rust-analyzer.rustfmt.overrideCommand (default: `null`):: 765+ 766-- 767Advanced option, fully override the command rust-analyzer uses for 768formatting. This should be the equivalent of `rustfmt` here, and 769not that of `cargo fmt`. The file contents will be passed on the 770standard input and the formatted result will be read from the 771standard output. 772-- 773[[rust-analyzer.rustfmt.rangeFormatting.enable]]rust-analyzer.rustfmt.rangeFormatting.enable (default: `false`):: 774+ 775-- 776Enables the use of rustfmt's unstable range formatting command for the 777`textDocument/rangeFormatting` request. The rustfmt option is unstable and only 778available on a nightly build. 779-- 780[[rust-analyzer.semanticHighlighting.doc.comment.inject.enable]]rust-analyzer.semanticHighlighting.doc.comment.inject.enable (default: `true`):: 781+ 782-- 783Inject additional highlighting into doc comments. 784 785When enabled, rust-analyzer will highlight rust source in doc comments as well as intra 786doc links. 787-- 788[[rust-analyzer.semanticHighlighting.nonStandardTokens]]rust-analyzer.semanticHighlighting.nonStandardTokens (default: `true`):: 789+ 790-- 791Whether the server is allowed to emit non-standard tokens and modifiers. 792-- 793[[rust-analyzer.semanticHighlighting.operator.enable]]rust-analyzer.semanticHighlighting.operator.enable (default: `true`):: 794+ 795-- 796Use semantic tokens for operators. 797 798When disabled, rust-analyzer will emit semantic tokens only for operator tokens when 799they are tagged with modifiers. 800-- 801[[rust-analyzer.semanticHighlighting.operator.specialization.enable]]rust-analyzer.semanticHighlighting.operator.specialization.enable (default: `false`):: 802+ 803-- 804Use specialized semantic tokens for operators. 805 806When enabled, rust-analyzer will emit special token types for operator tokens instead 807of the generic `operator` token type. 808-- 809[[rust-analyzer.semanticHighlighting.punctuation.enable]]rust-analyzer.semanticHighlighting.punctuation.enable (default: `false`):: 810+ 811-- 812Use semantic tokens for punctuation. 813 814When disabled, rust-analyzer will emit semantic tokens only for punctuation tokens when 815they are tagged with modifiers or have a special role. 816-- 817[[rust-analyzer.semanticHighlighting.punctuation.separate.macro.bang]]rust-analyzer.semanticHighlighting.punctuation.separate.macro.bang (default: `false`):: 818+ 819-- 820When enabled, rust-analyzer will emit a punctuation semantic token for the `!` of macro 821calls. 822-- 823[[rust-analyzer.semanticHighlighting.punctuation.specialization.enable]]rust-analyzer.semanticHighlighting.punctuation.specialization.enable (default: `false`):: 824+ 825-- 826Use specialized semantic tokens for punctuation. 827 828When enabled, rust-analyzer will emit special token types for punctuation tokens instead 829of the generic `punctuation` token type. 830-- 831[[rust-analyzer.semanticHighlighting.strings.enable]]rust-analyzer.semanticHighlighting.strings.enable (default: `true`):: 832+ 833-- 834Use semantic tokens for strings. 835 836In some editors (e.g. vscode) semantic tokens override other highlighting grammars. 837By disabling semantic tokens for strings, other grammars can be used to highlight 838their contents. 839-- 840[[rust-analyzer.signatureInfo.detail]]rust-analyzer.signatureInfo.detail (default: `"full"`):: 841+ 842-- 843Show full signature of the callable. Only shows parameters if disabled. 844-- 845[[rust-analyzer.signatureInfo.documentation.enable]]rust-analyzer.signatureInfo.documentation.enable (default: `true`):: 846+ 847-- 848Show documentation. 849-- 850[[rust-analyzer.typing.autoClosingAngleBrackets.enable]]rust-analyzer.typing.autoClosingAngleBrackets.enable (default: `false`):: 851+ 852-- 853Whether to insert closing angle brackets when typing an opening angle bracket of a generic argument list. 854-- 855[[rust-analyzer.workspace.symbol.search.kind]]rust-analyzer.workspace.symbol.search.kind (default: `"only_types"`):: 856+ 857-- 858Workspace symbol search kind. 859-- 860[[rust-analyzer.workspace.symbol.search.limit]]rust-analyzer.workspace.symbol.search.limit (default: `128`):: 861+ 862-- 863Limits the number of items returned from a workspace symbol search (Defaults to 128). 864Some clients like vs-code issue new searches on result filtering and don't require all results to be returned in the initial search. 865Other clients requires all results upfront and might require a higher limit. 866-- 867[[rust-analyzer.workspace.symbol.search.scope]]rust-analyzer.workspace.symbol.search.scope (default: `"workspace"`):: 868+ 869-- 870Workspace symbol search scope. 871--