diff options
| author | Aleksey Kladov <aleksey.kladov@gmail.com> | 2020-06-04 13:11:15 +0200 |
|---|---|---|
| committer | Aleksey Kladov <aleksey.kladov@gmail.com> | 2020-07-03 16:55:35 +0200 |
| commit | 058c1b60a5407d1932babe2ee5c8b32e65868567 (patch) | |
| tree | 272564c0e2a4f05c9e5ca07fc7e1d38e2010477a /src/libstd/sys/unix/process/process_unix.rs | |
| parent | cd1a46d644791c79433db934ad4e6131c577efcc (diff) | |
| download | rust-058c1b60a5407d1932babe2ee5c8b32e65868567.tar.gz rust-058c1b60a5407d1932babe2ee5c8b32e65868567.zip | |
Add rust-analyzer submodule
The current plan is that submodule tracks the `release` branch of rust-analyzer, which is updated once a week. rust-analyzer is a workspace (with a virtual manifest), the actual binary is provide by `crates/rust-analyzer` package. Note that we intentionally don't add rust-analyzer to `Kind::Test`, for two reasons. *First*, at the moment rust-analyzer's test suite does a couple of things which might not work in the context of rust repository. For example, it shells out directly to `rustup` and `rustfmt`. So, making this work requires non-trivial efforts. *Second*, it seems unlikely that running tests in rust-lang/rust repo would provide any additional guarantees. rust-analyzer builds with stable and does not depend on the specifics of the compiler, so changes to compiler can't break ra, unless they break stability guarantee. Additionally, rust-analyzer itself is gated on bors, so we are pretty confident that test suite passes.
Diffstat (limited to 'src/libstd/sys/unix/process/process_unix.rs')
0 files changed, 0 insertions, 0 deletions
