Whether to insert #[must_use] when generating as_ methods for enum variants.

Placeholder expression to use for missing expressions in assists.

Enable borrow checking for term search code assists. If set to false, also there will be more suggestions, but some of them may not borrow-check.

Term search fuel in "units of work" for assists (Defaults to 1800).

Warm up caches on project load.

How many worker threads to handle priming caches. The default 0 means to pick automatically.

Pass --all-targets to cargo invocation.

Automatically refresh project info via cargo metadata on Cargo.toml or .cargo/config.toml changes.

Run build scripts (build.rs) for more precise code analysis.

Specifies the invocation strategy to use when running the build scripts command. If per_workspace is set, the command will be executed for each Rust workspace with the workspace as the working directory. If once is set, the command will be executed once with the opened project as the working directory. This config only has an effect when rust-analyzer.cargo.buildScripts.overrideCommand is set.

Override the command rust-analyzer uses to run build scripts and build procedural macros. The command is required to output json and should therefore include --message-format=json or a similar option.

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.buildScripts.invocationStrategy.

By default, a cargo invocation will be constructed for the configured targets and features, with the following base command line:

.

Rerun proc-macros building/build-scripts running when proc-macro or build-script sources change and are saved.

Use RUSTC_WRAPPER=rust-analyzer when running build scripts to avoid checking unnecessary things.

Default:

List of cfg options to enable with the given values.

Extra arguments that are passed to every cargo invocation.

Extra environment variables that will be set when running cargo, rustc or other commands within the workspace. Useful for setting RUSTFLAGS.

List of features to activate.

Set this to "all" to pass --all-features to cargo.

Whether to pass --no-default-features to cargo.

Relative path to the sysroot, or "discover" to try to automatically find it via "rustc --print sysroot".

Unsetting this disables sysroot loading.

This option does not take effect until rust-analyzer is restarted.

Relative path to the sysroot library sources. If left unset, this will default to {cargo.sysroot}/lib/rustlib/src/rust/library.

This option does not take effect until rust-analyzer is restarted.

Compilation target override (target triple).

Optional path to a rust-analyzer specific target directory. This prevents rust-analyzer’s cargo check and initial build-script and proc-macro building from locking the Cargo.lock at the expense of duplicating build artifacts.

Set to true to use a subdirectory of the existing target directory or set to a path relative to the workspace to use that path.

Set cfg(test) for local crates. Defaults to true.

Run the check command for diagnostics on save.

Check all targets and tests (--all-targets). Defaults to rust-analyzer.cargo.allTargets.

Cargo command to use for cargo check.

Extra arguments for cargo check.

Extra environment variables that will be set when running cargo check. Extends rust-analyzer.cargo.extraEnv.

List of features to activate. Defaults to rust-analyzer.cargo.features.

Set to "all" to pass --all-features to Cargo.

List of cargo check (or other command specified in check.command) diagnostics to ignore.

For example for cargo check: dead_code, unused_imports, unused_variables,…​

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.check.overrideCommand is set.

Whether to pass --no-default-features to Cargo. Defaults to rust-analyzer.cargo.noDefaultFeatures.

Override the command rust-analyzer uses instead of cargo check for diagnostics on save. The command is required to output json and should therefore include --message-format=json or a similar option (if your client supports the colorDiagnosticOutput experimental capability, you can use --message-format=json-diagnostic-rendered-ansi).

If you’re changing this because you’re using some tool wrapping Cargo, you might also want to change rust-analyzer.cargo.buildScripts.overrideCommand.

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.check.invocationStrategy.

If $saved_file is part of the command, rust-analyzer will pass the absolute path of the saved file to the provided command. This is intended to be used with non-Cargo build systems. Note that $saved_file is experimental and may be removed in the future.

An example command would be:

.

Check for specific targets. Defaults to rust-analyzer.cargo.target if empty.

Can be a single target, e.g. "x86_64-unknown-linux-gnu" or a list of targets, e.g. ["aarch64-apple-darwin", "x86_64-apple-darwin"].

Aliased as "checkOnSave.targets".

Whether --workspace should be passed to cargo check. If false, -p <package> will be passed instead.

Whether to automatically add a semicolon when completing unit-returning functions.

In match arms it completes a comma instead.

Toggles the additional completions that automatically add imports when completed. Note that your client must specify the additionalTextEdits LSP client capability to truly have this feature enabled.

Toggles the additional completions that automatically show method calls and field accesses with self prefixed to them when inside a method.

Whether to add parenthesis and argument snippets when completing function.

Whether to show full function/method signatures in completion docs.

Whether to omit deprecated items from autocompletion. By default they are marked as deprecated but not hidden.

Maximum number of completions to return. If None, the limit is infinite.

Whether to show postfix snippets like dbg, if, not, etc.

Enables completions of private items and fields that are defined in the current workspace even if they are not visible at the current position.

Default:

Custom completion snippets.

Whether to enable term search based snippets like Some(foo.bar().baz()).

Term search fuel in "units of work" for autocompletion (Defaults to 1000).

List of rust-analyzer diagnostics to disable.

Whether to show native rust-analyzer diagnostics.

Whether to show experimental rust-analyzer diagnostics that might have more false positives than usual.

Map of prefixes to be substituted when parsing diagnostic file paths. This should be the reverse mapping of what is passed to rustc as --remap-path-prefix.

Whether to run additional style lints.

List of warnings that should be displayed with hint severity.

The warnings will be indicated by faded text or three dots in code and will not show up in the Problems Panel.

List of warnings that should be displayed with info severity.

The warnings will be indicated by a blue squiggly underline in code and a blue icon in the Problems Panel.

These directories will be ignored by rust-analyzer. They are relative to the workspace root, and globs are not supported. You may also need to add the folders to Code’s files.watcherExclude.

Controls file watching implementation.

Enables highlighting of related references while the cursor is on break, loop, while, or for keywords.

Enables highlighting of all captures of a closure while the cursor is on the | or move keyword of a closure.

Enables highlighting of all exit points while the cursor is on any return, ?, fn, or return type arrow (→).

Enables highlighting of related references while the cursor is on any identifier.

Enables highlighting of all break points for a loop or block context while the cursor is on any async or await keywords.

Whether to show Debug action. Only applies when rust-analyzer.hover.actions.enable is set.

Whether to show HoverActions in Rust files.

Whether to show Go to Type Definition action. Only applies when rust-analyzer.hover.actions.enable is set.

Whether to show Implementations action. Only applies when rust-analyzer.hover.actions.enable is set.

Whether to show References action. Only applies when rust-analyzer.hover.actions.enable is set.

Whether to show Run action. Only applies when rust-analyzer.hover.actions.enable is set.

Whether to show documentation on hover.

Whether to show keyword hover popups. Only applies when rust-analyzer.hover.documentation.enable is set.

Use markdown syntax for links on hover.

How to render the align information in a memory layout hover.

Whether to show memory layout data on hover.

How to render the niche information in a memory layout hover.

How to render the offset information in a memory layout hover.

How to render the size information in a memory layout hover.

How many variants of an enum to display when hovering on. Show none if empty.

How many fields of a struct, variant or union to display when hovering on. Show none if empty.

How many associated items of a trait to display when hovering a trait.

Whether to enforce the import granularity setting for all files. If set to false rust-analyzer will try to keep import styles consistent per file.

How imports should be grouped into use statements.

Group inserted imports by the following order. Groups are separated by newlines.

Whether to allow import insertion to merge new imports into single path glob imports like use std::fmt::*;.

Prefer to unconditionally use imports of the core and alloc crate, over the std crate.

Whether to prefer import paths containing a prelude module.

The path structure for newly inserted paths to use.

Whether to prefix external (including std, core) crate imports with ::. e.g. "use ::std::io::Read;".

Whether to show inlay type hints for binding modes.

Whether to show inlay type hints for method chains.

Whether to show inlay hints after a closing } to indicate what item it belongs to.

Minimum number of lines required before the } until the hint is shown (set to 0 or 1 to always show them).

Whether to show inlay hints for closure captures.

Whether to show inlay type hints for return types of closures.

Closure notation in type and chaining inlay hints.

Whether to show enum variant discriminant hints.

Whether to show inlay hints for type adjustments.

Whether to hide inlay hints for type adjustments outside of unsafe blocks.

Whether to show inlay hints as postfix ops (. instead of , etc).

Whether to show const generic parameter name inlay hints.

Whether to show generic lifetime parameter name inlay hints.

Whether to show generic type parameter name inlay hints.

Whether to show implicit drop hints.

Whether to show inlay type hints for elided lifetimes in function signatures.

Whether to prefer using parameter names as the name for elided lifetime hints if possible.

Maximum length for inlay hints. Set to null to have an unlimited length.

Whether to show function parameter name inlay hints at the call site.

Whether to show exclusive range inlay hints.

Whether to show inlay hints for compiler inserted reborrows. This setting is deprecated in favor of rust-analyzer.inlayHints.expressionAdjustmentHints.enable.

Whether to render leading colons for type hints, and trailing colons for parameter hints.

Whether to show inlay type hints for variables.

Whether to hide inlay type hints for let statements that initialize to a closure. Only applies to closures with blocks, same as rust-analyzer.inlayHints.closureReturnTypeHints.enable.

Whether to hide inlay type hints for constructors.

Enables the experimental support for interpreting tests.

Join lines merges consecutive declaration and initialization of an assignment.

Join lines inserts else between consecutive ifs.

Join lines removes trailing commas.

Join lines unwraps trivial blocks.

Whether to show Debug lens. Only applies when rust-analyzer.lens.enable is set.

Whether to show CodeLens in Rust files.

Whether to show Implementations lens. Only applies when rust-analyzer.lens.enable is set.

Where to render annotations.

Whether to show References lens for Struct, Enum, and Union. Only applies when rust-analyzer.lens.enable is set.

Whether to show References lens for Enum Variants. Only applies when rust-analyzer.lens.enable is set.

Whether to show Method References lens. Only applies when rust-analyzer.lens.enable is set.

Whether to show References lens for Trait. Only applies when rust-analyzer.lens.enable is set.

Whether to show Run lens. Only applies when rust-analyzer.lens.enable is set.

Disable project auto-discovery in favor of explicitly specified set of projects.

Elements must be paths pointing to Cargo.toml, rust-project.json, .rs files (which will be treated as standalone files) or JSON objects in rust-project.json format.

Number of syntax trees rust-analyzer keeps in memory. Defaults to 128.

Sets the LRU capacity of the specified queries.

Whether to show can’t find Cargo.toml error message.

How many worker threads in the main loop. The default null means to pick automatically.

Expand attribute macros. Requires rust-analyzer.procMacro.enable to be set.

Enable support for procedural macros, implies rust-analyzer.cargo.buildScripts.enable.

These proc-macros will be ignored when trying to expand them.

This config takes a map of crate names with the exported proc-macro names to ignore as values.

Internal config, path to proc-macro server executable.

Exclude imports from find-all-references.

Exclude tests from find-all-references.

Command to be executed instead of 'cargo' for runnables.

Additional arguments to be passed to cargo for runnables such as tests or binaries. For example, it may be --release.

Default:

Additional arguments to be passed through Cargo to launched tests, benchmarks, or doc-tests.

Unless the launched target uses a [custom test harness](https://doc.rust-lang.org/cargo/reference/cargo-targets.html#the-harness-field), they will end up being interpreted as options to [rustc’s built-in test harness (“libtest”)](https://doc.rust-lang.org/rustc/tests/index.html#cli-arguments).

Path to the Cargo.toml of the rust compiler workspace, for usage in rustc_private projects, or "discover" to try to automatically find it if the rustc-dev component is installed.

Any project which uses rust-analyzer with the rustcPrivate crates must set [package.metadata.rust-analyzer] rustc_private=true to use it.

This option does not take effect until rust-analyzer is restarted.

Additional arguments to rustfmt.

Advanced option, fully override the command rust-analyzer uses for formatting. This should be the equivalent of rustfmt here, and not that of cargo fmt. The file contents will be passed on the standard input and the formatted result will be read from the standard output.

Enables the use of rustfmt’s unstable range formatting command for the textDocument/rangeFormatting request. The rustfmt option is unstable and only available on a nightly build.

Inject additional highlighting into doc comments.

When enabled, rust-analyzer will highlight rust source in doc comments as well as intra doc links.

Whether the server is allowed to emit non-standard tokens and modifiers.

Use semantic tokens for operators.

When disabled, rust-analyzer will emit semantic tokens only for operator tokens when they are tagged with modifiers.

Use specialized semantic tokens for operators.

When enabled, rust-analyzer will emit special token types for operator tokens instead of the generic operator token type.

Use semantic tokens for punctuation.

When disabled, rust-analyzer will emit semantic tokens only for punctuation tokens when they are tagged with modifiers or have a special role.

When enabled, rust-analyzer will emit a punctuation semantic token for the ! of macro calls.

Use specialized semantic tokens for punctuation.

When enabled, rust-analyzer will emit special token types for punctuation tokens instead of the generic punctuation token type.

Use semantic tokens for strings.

In some editors (e.g. vscode) semantic tokens override other highlighting grammars. By disabling semantic tokens for strings, other grammars can be used to highlight their contents.

Show full signature of the callable. Only shows parameters if disabled.

Show documentation.

Whether to insert closing angle brackets when typing an opening angle bracket of a generic argument list.

Enables automatic discovery of projects using [DiscoverWorkspaceConfig::command].

[DiscoverWorkspaceConfig] also requires setting progress_label and files_to_watch. progress_label is used for the title in progress indicators, whereas files_to_watch is used to determine which build system-specific files should be watched in order to reload rust-analyzer.

Below is an example of a valid configuration:

## On DiscoverWorkspaceConfig::command

Warning: This format is provisional and subject to change.

[DiscoverWorkspaceConfig::command] must return a JSON object corresponding to DiscoverProjectData::Finished:

As JSON, DiscoverProjectData::Finished is:

It is encouraged, but not required, to use the other variants on DiscoverProjectData to provide a more polished end-user experience.

DiscoverWorkspaceConfig::command may optionally include an {arg}, which will be substituted with the JSON-serialized form of the following enum:

The JSON representation of DiscoverArgument::Path is:

Similarly, the JSON representation of DiscoverArgument::Buildfile is:

DiscoverArgument::Path is used to find and generate a rust-project.json, and therefore, a workspace, whereas DiscoverArgument::buildfile is used to to update an existing workspace. As a reference for implementors, buck2’s rust-project will likely be useful: https://github.com/facebook/buck2/tree/main/integrations/rust-project.

Workspace symbol search kind.

Limits the number of items returned from a workspace symbol search (Defaults to 128). Some clients like vs-code issue new searches on result filtering and don’t require all results to be returned in the initial search. Other clients requires all results upfront and might require a higher limit.

Workspace symbol search scope.