diff options
| author | bors <bors@rust-lang.org> | 2023-11-16 17:43:14 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-16 17:43:14 +0000 |
| commit | 37a87908295b481374ab6f7cd049e7a5fe6fa409 (patch) | |
| tree | 54fb70c98d95156d5ead3b57d831c167d1802aca /compiler/rustc_llvm/llvm-wrapper/SymbolWrapper.cpp | |
| parent | 58de0b130a763f3a2d373f508ac0c18a8e7d0acd (diff) | |
| parent | 0cd68bfed3e31c034a5ead664ac8ad84d8bc06fd (diff) | |
| download | rust-37a87908295b481374ab6f7cd049e7a5fe6fa409.tar.gz rust-37a87908295b481374ab6f7cd049e7a5fe6fa409.zip | |
Auto merge of #15830 - davidbarsky:davidbarsky/allow-companion-extension-to-call-rust-analyzer, r=davidbarsky
code: expose workspaces to other extensions; remove `addProject` command
This (mostly red) PR does three things:
- Exposes two methods to companion extensions (`setWorkspaces` and `notifyRustAnalyzer`).
- `setWorkspaces` is needed to update `linkedProjects` _without_ writing workspace/global configuration.
- `notifyRustAnalyzer` to get the server to pull the new configuration.
- Makes `Ctx` implement `RustAnalyzerExtensionApi` to prevent accidental regressions.
- Remove `rust-analyzer.addProject`, as that will live in a buck2 companion extension. No need for that to be in rust-analyzer!
I can see the utility of combining `notifyRustAnalyzer` and `setWorkspaces` into a single method (`updateWorkspacesAndNotify()`?), but I don't feel strongly about this. My feeling is that this API could be easily changed in the future.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/SymbolWrapper.cpp')
0 files changed, 0 insertions, 0 deletions