| .. | ||
| contributing | ||
| assists.md | ||
| configuration.md | ||
| configuration_generated.md | ||
| diagnostics.md | ||
| editor_features.md | ||
| faq.md | ||
| features.md | ||
| installation.md | ||
| non_cargo_based_projects.md | ||
| other_editors.md | ||
| privacy.md | ||
| README.md | ||
| rust_analyzer_binary.md | ||
| security.md | ||
| SUMMARY.md | ||
| troubleshooting.md | ||
| vs_code.md | ||
rust-analyzer
At its core, rust-analyzer is a library for semantic analysis of Rust code as it changes over time. This manual focuses on a specific usage of the library -- running it as part of a server that implements the Language Server Protocol (LSP). The LSP allows various code editors, like VS Code, Emacs or Vim, to implement semantic features like completion or goto definition by talking to an external language server process.
To improve this document, send a pull request: https://github.com/rust-lang/rust-analyzer
The manual is written in markdown and includes
some extra files which are generated from the source code. Run
cargo test and cargo xtask codegen to create these.
If you have questions about using rust-analyzer, please ask them in the "IDEs and Editors" topic of Rust users forum.