This documents is an index of features that rust-analyzer language server provides. Shortcuts are for the default VS Code layout. If there's no shortcut, you can use Ctrl+Shift+P to search for the corresponding action.
Uses fuzzy-search to find types, modules and function by name across your
project and dependencies. This is the most useful feature, which improves code
navigation tremendously. It mostly works on top of the built-in LSP
functionality, however # and * symbols can be used to narrow down the
search. Specifically,
Foosearches forFootype in the current workspacefoo#searches forfoofunction in the current workspaceFoo*searches forFootype among dependencies, includingstdlibfoo#*searches forfoofunction among dependencies.
That is, # switches from "types" to all symbols, * switches from the current
workspace to dependencies.
Provides a tree of the symbols defined in the file. Can be used to
- fuzzy search symbol in a file (super useful)
- draw breadcrumbs to describe the context around the cursor
- draw outline of the file
Some features trigger on typing certain characters:
- typing
let =tries to smartly add;if=is followed by an existing expression. - Enter inside comments automatically inserts
/// - typing
.in a chain method call auto-indents
Extends the current selection to the encompassing syntactic construct (expression, statement, item, module, etc). It works with multiple cursors. This is a relatively new feature of LSP: microsoft/language-server-protocol#613, check your editor's LSP library to see if this feature is supported.
Navigates to the definition of an identifier.
Navigates to the impl block of structs, enums or traits. Also implemented as a code lens.
Navigates to the type of an identifier.
Shows popup suggesting to run a test/benchmark/binary at the current cursor location. Super useful for repeatedly running just a single test. Do bind this to a shortcut!
Navigates to the parent module of the current module.
If the cursor is on any brace (<>(){}[]) which is a part of a brace-pair,
moves cursor to the matching brace. It uses the actual parser to determine
braces, so it won't confuse generics with comparisons.
Join selected lines into one, smartly fixing up whitespace and trailing commas.
Shows the parse tree of the current file. It exists mostly for debugging rust-analyzer itself.
Shows the full macro expansion of the macro at current cursor.
Shows internal statistic about memory usage of rust-analyzer
Manually triggers GC
Start cargo watch for live error highlighting. Will prompt to install if it's not already installed.
Stop cargo watch
Assists, or code actions, are small local refactorings, available in a particular context. They are usually triggered by a shortcut or by clicking a light bulb icon in the editor.
See assists.md for the list of available assists.
In addition to usual reference completion, rust-analyzer provides some ✨magic✨ completions as well:
Keywords like if, else while, loop are completed with braces, and cursor
is placed at the appropriate position. Even though if is easy to type, you
still want to complete it, to get { } for free! return is inserted with a
space or ; depending on the return type of the function.
When completing a function call, () are automatically inserted. If function
takes arguments, cursor is positioned inside the parenthesis.
There are postifx completions, which can be triggerd by typing something like
foo().if. The word after . determines postifx completion, possible variants are:
expr.if->if expr {}expr.match->match expr {}expr.while->while expr {}expr.ref->&exprexpr.refm->&mut exprexpr.not->!exprexpr.dbg->dbg!(expr)
There also snippet completions:
pd->println!("{:?}")ppd->println!("{:#?}")
tfn->#[test] fn f(){}
Experimental feature to let rust-analyzer highlight Rust code instead of using the default highlighter.
Experimental feature that, given code highlighting using rust-analyzer is active, will pick unique colors for identifiers.