Go to file
bors[bot] 04d2b7b256
Merge #5565
5565: SSR: Don't mix non-path-based rules with path-based r=matklad a=davidlattimore

If any rules contain paths, then we reject any rules that don't contain paths. Allowing a mix leads to strange semantics, since the path-based rules only match things where the path refers to semantically the same thing, whereas the non-path-based rules could match anything. Specifically, if we have a rule like `foo ==>> bar` we only want to match the `foo` that is in the current scope, not any `foo`. However "foo" can be parsed as a pattern (BIND_PAT -> NAME -> IDENT). Allowing such a rule through would result in renaming everything called `foo` to `bar`. It'd also be slow, since without a path, we'd have to use the slow-scan search mechanism.

Co-authored-by: David Lattimore <dml@google.com>
2020-07-29 08:55:34 +00:00
.cargo
.github Fix metrics 2020-07-24 20:53:27 +02:00
.vscode vscode client side tests 2020-05-20 22:31:39 +03:00
crates Merge #5565 2020-07-29 08:55:34 +00:00
docs README: Add some instructions for running typescript tests and linter. 2020-07-25 09:35:33 +10:00
editors/code Add toggle for experimental diagnostics 2020-07-24 17:39:16 +02:00
xtask Add rustc-perf to metrics 2020-07-25 10:35:45 +02:00
.gitattributes Update .gitattributes 2020-07-20 12:45:05 +02:00
.gitignore Remove html from gitignore so highlight snapshots are not ignored 2020-06-27 12:02:49 -04:00
bors.toml Fix bors config? 2020-05-24 16:07:46 +02:00
Cargo.lock ⬆️ deps 2020-07-27 09:30:44 +02:00
Cargo.toml Gzip artifacts 2020-07-07 23:30:11 +03:00
LICENSE-APACHE
LICENSE-MIT
README.md Link metrics 2020-07-25 00:18:21 +02:00
rustfmt.toml

rust-analyzer logo

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.

Work on rust-analyzer is sponsored by

Ferrous Systems

Quick Start

https://rust-analyzer.github.io/manual.html#installation

Documentation

If you want to contribute to rust-analyzer or are 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 the manual folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.

Communication

For usage and troubleshooting requests, please use "IDEs and Editors" category of the Rust forum:

https://users.rust-lang.org/c/ide/14

For questions about development and implementation, join rls-2.0 working group on Zulip:

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

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.