diff options
| author | bors <bors@rust-lang.org> | 2023-03-30 13:38:36 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-03-30 13:38:36 +0000 |
| commit | d3b129f04fcf635078738d7efca52566a00e4354 (patch) | |
| tree | 9fd9ecad5039d40af46838cfa2b8f9fb0a664edd /tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.panic-unwind.diff | |
| parent | 562477b4da54cfb9756a44328ceb51f0e10fb641 (diff) | |
| parent | fb9a1dd87ed3c44bb261958fbe2111f19e9185c9 (diff) | |
| download | rust-d3b129f04fcf635078738d7efca52566a00e4354.tar.gz rust-d3b129f04fcf635078738d7efca52566a00e4354.zip | |
Auto merge of #14444 - zapkub:runable-debug-env-is-not-passing-properly, r=Veykril
Missing runnable env on debug target
Fix bug in Rust Analyzer VSCode where runnable debugging did not pass
environment variable from configuration to child process of Cargo on binary build stage
There is a missing env passing along to `cargo` in debug target which give an in-consistent result from debug and run target
For example
```json
{
"rust-analyzer.runnableEnv": {
"OUT_DIR": "/test/path2"
}
}
```
## run
## debug
compiling binary is failed. Missing env
## debug (after fix)
Diffstat (limited to 'tests/mir-opt/lower_array_len.array_len.NormalizeArrayLen.panic-unwind.diff')
0 files changed, 0 insertions, 0 deletions