diff options
| author | bors <bors@rust-lang.org> | 2023-07-24 16:29:18 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-07-24 16:29:18 +0000 |
| commit | b64e5b3919b24bc784f36248e6e1f921ee7bb71b (patch) | |
| tree | 46e5961c769fcc03ff91198fa126d4fc15857077 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | febb3b31ce92e5d5390751bb6329f8488bf6ce77 (diff) | |
| parent | ba722165a06b5d325f7612192efb8c5425a33253 (diff) | |
| download | rust-b64e5b3919b24bc784f36248e6e1f921ee7bb71b.tar.gz rust-b64e5b3919b24bc784f36248e6e1f921ee7bb71b.zip | |
Auto merge of #15333 - davidbarsky:davidbarsky/downgrade-vscode-to-1.75, r=lnicola
vscode: change minimum VS Code version to 1.75 from 1.78 I previously mentioned [in a comment](https://github.com/rust-lang/rust-analyzer/pull/15265#issuecomment-1633240290) that folks at my employer are on 1.78, but I was incorrect: people are on 1.75. I know this is outside the standard version support policy, but I haven't seen any of the new features in VS Code be used in rust-analyzer. The most applicable feature in those three versions of VS Code that I can find [is lazily resolving code actions](https://code.visualstudio.com/updates/v1_78#_resolve-code-action-commands-in-resolvecodeaction), but it doesn't seem like rust-analyzer is making use of that feature. (I'll be posting a PR that adds support for `$saved_file` within the next day, so feel free to bump the minimum VS Code version back to 1.78 if/when that PR lands. This just makes vendoring the _actual_ change I'm interested in a little bit easier.)
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions