diff options
| author | Jacob Pratt <jacob@jhpratt.dev> | 2024-12-01 21:38:26 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-01 21:38:26 -0500 |
| commit | 76183a53ed49264769c1e27296eee6115a1e43c1 (patch) | |
| tree | 99203dee6dd56d84f2b267f56f3e50d1103f46a9 /compiler/rustc_mir_transform/src | |
| parent | 1391039fa763b517b04fa73df87bb9afdab7b1c3 (diff) | |
| parent | fd1371781540c3b58bb3ee0f0ce17ad134b11926 (diff) | |
| download | rust-76183a53ed49264769c1e27296eee6115a1e43c1.tar.gz rust-76183a53ed49264769c1e27296eee6115a1e43c1.zip | |
Rollup merge of #133712 - RalfJung:rust_analyzer_settings, r=jieyouxu
rust_analyzer_settings: force use of 'nightly' toolchain The cranelift folder contains a rust-toolchain file. That means when RA opens `compiler/rustc_codegen_cranelift/Cargo.toml`, it will try to use that toolchain or fail. (Maybe that toolchain gets auto-installed for others? On my system, it just fails, but I also run vscodium in a sandbox.) However, it shouldn't be necessary to use more than one toolchain for the rustc workspace. So we can set the `RUSTUP_TOOLCHAIN` variable on the server side to force the same toolchain to be used everywhere. Suggested by `@ChayimFriedman2` in https://github.com/rust-lang/rust-analyzer/issues/18585.
Diffstat (limited to 'compiler/rustc_mir_transform/src')
0 files changed, 0 insertions, 0 deletions