commit | a5ae50400dbab3f176a640570d336dae91d4e16e | [log] [tgz] |
---|---|---|
author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | Mon Jul 06 10:56:22 2020 +0000 |
committer | GitHub <noreply@github.com> | Mon Jul 06 10:56:22 2020 +0000 |
tree | 276513ea550ae27a284321e3f35b2ff46f545f1d | |
parent | a0f24455ddc474ee288849b79aa1fc8ca7829385 [diff] | |
parent | ef223b9e6439c228e0be49861efd2067c0b22af4 [diff] |
Merge #5234 5234: Fix: allow for binaries from $PATH to pass validity check r=matklad a=Veetaha Tackles https://github.com/rust-analyzer/rust-analyzer/pull/5229#issuecomment-654151387 cc @matklad @lnicola Apparently `fs.existsSync()` works only with real paths and not with `$PATH` env var Co-authored-by: Veetaha <veetaha2@gmail.com>
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:
https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Fwg-rls-2.2E0
Work on rust-analyzer is sponsored by
https://rust-analyzer.github.io/manual.html#installation
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.
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
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.