mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
16,903 Commits 2 Branches 0 Tags 1.4 GiB
Rust 96.2%
RenderScript 0.7%
JavaScript 0.6%
Shell 0.6%
Fluent 0.4%
Other 1.3%
c4664609ed
Go to file
Brendan Cully c4664609ed Use package root as cargo check working directory 
Cargo commands are affected by the `.cargo/config` files above
their working directory. If cargo is invoked from above the directory
holding `Cargo.toml`, it may not pick up important settings like
registry replacements, causing it to behave differently or even fail.

Most cargo invocations are currently setting their working directories
to the directory containing `Cargo.toml`, but a couple of paths remain
in which cargo is invoked from the default workspace root instead.

This change fixes that, resolving some cargo check failures that I
experienced in a multi-root workspace in which packages used different
registries.
2021-05-12 19:50:52 -07:00
.cargo xtask: replace "lint" command by a simply cargo alias 2021-03-14 13:36:45 +01:00
.github Merge #8427 2021-05-03 13:37:12 +00:00
.vscode Add "Win Attach to Server" debug configuration 2021-01-25 17:46:03 +03:00
assets
bench_data Add benchmark test for mbe 2021-02-25 05:47:13 +08:00
crates Use package root as cargo check working directory 2021-05-12 19:50:52 -07:00
docs Document viewCrateGraph request 2021-05-11 16:45:51 +02:00
editors/code Allow viewing the crate graph in a webview 2021-05-11 16:15:31 +02:00
lib Intern GenericParams 2021-04-05 03:50:10 +02:00
xtask fix: direct people to the right repository 2021-05-08 00:26:29 +03:00
.gitattributes
.gitignore
bors.toml
Cargo.lock Allow viewing the crate graph in a webview 2021-05-11 16:15:31 +02:00
Cargo.toml internal: use modern resolever 2021-05-11 13:06:35 +03:00
LICENSE-APACHE
LICENSE-MIT
PRIVACY.md Update Zulip link and macro privacy statement 2021-04-06 21:42:27 +03:00
README.md Update Zulip link and macro privacy statement 2021-04-06 21:42:27 +03:00
rustfmt.toml

README.md

rust-analyzer logo

rust-analyzer is a 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 rust-analyzer working group on Zulip:

https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer

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.