Go to file

Pascal Hertleif 5bf3e949e8 Semantic highlighting spike Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?		2019-05-27 11:26:33 +02:00
.cargo	Add `cargo jinstall-lsp` as a shorthand to include jemalloc support	2019-01-29 17:02:06 +00:00
.vscode	revert change to "check" since "build" is intentional	2019-03-10 14:57:30 +01:00
crates	Semantic highlighting spike	2019-05-27 11:26:33 +02:00
docs	Add Vim and NeoVim setup section	2019-05-25 18:55:59 -03:00
editors	Semantic highlighting spike	2019-05-27 11:26:33 +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	Use Xenial image and fix find call	2019-05-23 16:05:01 +03:00
bors.toml	remove appveyor	2019-04-21 19:26:01 +03:00
Cargo.lock	Add Either dep	2019-05-26 20:10:05 +08:00
Cargo.toml	⬆️ lsp	2019-04-21 15:17:22 +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.