mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
10,304 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%
9feb15e6a2
Go to file
bors[bot] 9feb15e6a2
Merge #4669 
4669: Always derive from `process.env` when spawning a child process/shell execution r=matklad a=Dfinity-Alin

This is useful when an extension (e.g. [Nix Environment Selector](https://marketplace.visualstudio.com/items?itemName=arrterian.nix-env-selector)) or [launch
configuration](https://stackoverflow.com/questions/57641460/set-env-var-for-node-js-when-launching-through-vs-code) sets one or more environment variables.

When `env` is not explicitly specified in the options passed to
`child_process.spawn()` or `vscode.ShellExecution()`, then `process.env` gets
applied automatically. But when an explicit `env` is set, it should inherit from
`process.env` rather than replace it completely.

Co-authored-by: Alin Sinpalean <alin.sinpalean@dfinity.org>
2020-05-31 16:58:57 +00:00
.cargo Alternative quite tests alias 2019-11-20 22:22:32 +03:00
.github Fix conflict between nightly branch and tag 2020-05-25 16:31:19 +02:00
.vscode vscode client side tests 2020-05-20 22:31:39 +03:00
crates Merge #4667 2020-05-31 12:03:24 +00:00
docs Link to the specific source line 2020-05-31 15:36:20 +02:00
editors/code Always derive from process.env when spawning a child process/shell execution 2020-05-31 13:41:55 +02:00
xtask Merge #4672 2020-05-31 13:36:52 +00:00
.gitattributes Set text to autodetect and use LF 2019-11-14 19:44:37 -05:00
.gitignore Ignore HTML 2020-05-31 09:29:15 +02:00
bors.toml Fix bors config? 2020-05-24 16:07:46 +02:00
Cargo.lock Update deps 2020-05-31 11:38:09 -04:00
Cargo.toml Upgrade Chalk 2020-05-27 21:07:08 +02: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 Link forum topic 2020-05-28 10:19:01 +02:00
rustfmt.toml Remove forcing \n via rustfmt 2019-11-02 22:19:59 +03:00

README.md

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. 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

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

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.