diff options
| author | bors <bors@rust-lang.org> | 2024-10-12 07:45:15 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-10-12 07:45:15 +0000 |
| commit | aacf840ea6914e0dfe31406972174ee945e763cf (patch) | |
| tree | 563830ed094b4d9b3a08df018b8356f754e9eb9b /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 7562b175e35cd4f838fc623b15dda2b9cb5555c0 (diff) | |
| parent | 0460ff71b2470f24c77c2f6aafd60a6f88afa800 (diff) | |
| download | rust-aacf840ea6914e0dfe31406972174ee945e763cf.tar.gz rust-aacf840ea6914e0dfe31406972174ee945e763cf.zip | |
Auto merge of #18281 - darichey:async-subprocess, r=lnicola
Run subprocesses async in vscode extension Extensions should not block the vscode extension host. Replace uses of `spawnSync` with `spawnAsync`, a convenience wrapper around `spawn`. These `spawnSync`s are unlikely to cause a real issue in practice, because they spawn very short-lived processes, so we aren't blocking for very long. That said, blocking the extension host is poor practice, and if they _do_ block for too long for whatever reason, vscode becomes useless.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
