Go to file

Aleksey Kladov 6314e62cfb add analysis-bench to benchmark incremental analysis Can be used like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --complete ../chalk/chalk-engine/src/logic.rs:94:0 loading: 225.970093ms from scratch: 8.492373325s no change: 445.265µs trivial change: 95.631242ms ``` Or like this: ``` $ cargo run --release -p ra_cli -- \ analysis-bench ../chalk/ \ --highlight ../chalk/chalk-engine/src/logic.rs loading: 209.873484ms from scratch: 9.504916942s no change: 7.731119ms trivial change: 124.984039ms ``` "from scratch" includes initial analysis of the relevant bits of the project "no change" just asks the same question for the second time. It measures overhead on assembling the answer outside of salsa. "trivial change" doesn't do an actual salsa change, it just advances the revision. This test how fast is salsa at validating things.		2019-06-16 19:45:05 +03:00
.cargo	rename tools -> ra_tools	2019-06-11 01:47:37 +03:00
.vscode	revert change to "check" since "build" is intentional	2019-03-10 14:57:30 +01:00
crates	add analysis-bench to benchmark incremental analysis	2019-06-16 19:45:05 +03:00
docs	add analysis-bench to benchmark incremental analysis	2019-06-16 19:45:05 +03:00
editors	ra-emacs-lsp: Fix company-lsp snippet handler override	2019-06-14 20:58:03 +02:00
.gitattributes	add .gitattributes	2019-04-05 23:31:58 +08:00
.gitignore	Updated the gitignore	2019-04-05 22:06:15 +01:00
.travis.yml	don't remove tools from cache	2019-05-30 10:17:29 +03:00
bors.toml	remove appveyor	2019-04-21 19:26:01 +03:00
Cargo.lock	Merge #1408	2019-06-16 12:00:41 +00:00
Cargo.toml	⬆️ salsa	2019-06-07 09:44:28 +03:00
LICENSE-APACHE	Licenses	2018-01-10 22:47:04 +03:00
LICENSE-MIT	Licenses	2018-01-10 22:47:04 +03:00
README.md	fix logo	2019-05-21 17:43:24 +03:00
rustfmt.toml	enable "small heuristics"	2019-02-08 14:49:26 +03:00

README.md

Rust Analyzer

Rust Analyzer is an experimental modular compiler frontend for the Rust language. It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust. If you want to get involved, check the rls-2.0 working group in the compiler-team repository:

https://github.com/rust-lang/compiler-team/tree/master/working-groups/rls-2.0

Work on the Rust Analyzer is sponsored by

Mozilla

Language Server Quick Start

Rust Analyzer is a work-in-progress, so you'll have to build it from source, and you might encounter critical bugs. That said, it is complete enough to provide a useful IDE experience and some people use it as a daily driver.

To build rust-analyzer, you need:

latest stable rust for language server itself
latest stable npm and VS Code for VS Code extension (code should be in path)

For setup for other editors, see ./docs/user.

# clone the repo
$ git clone https://github.com/rust-analyzer/rust-analyzer && cd rust-analyzer

# install both the language server and VS Code extension
$ cargo install-code

# alternatively, install only the server. Binary name is `ra_lsp_server`.
$ cargo install-lsp

Documentation

If you want to contribute to rust-analyzer or just curious about how things work under the hood, check the ./docs/dev folder.

If you want to use rust-analyzer's language server with your editor of choice, check ./docs/user folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.

Getting in touch

We are on the rust-lang Zulip!

https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frls-2.2E0

Quick Links

License

Rust analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.