diff options
| author | bors <bors@rust-lang.org> | 2023-10-06 11:33:52 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-10-06 11:33:52 +0000 |
| commit | b1f89a84ab350091e6c20cfe30c2fab8d76b80e4 (patch) | |
| tree | e1ee6a89037e97acbfd9a2af43d8ee771dff995d /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | ef58843b9fe5d580fcaf29d8231fa607deea175f (diff) | |
| parent | b3ebc9ab6a0793612d75d3587f9de3522f6a71bb (diff) | |
| download | rust-b1f89a84ab350091e6c20cfe30c2fab8d76b80e4.tar.gz rust-b1f89a84ab350091e6c20cfe30c2fab8d76b80e4.zip | |
Auto merge of #15600 - davidbarsky:davidbarsky/broken-rustfmt-in-ra, r=Veykril
fix: ensure `rustfmt` runs when configured with `./`
(Hopefully) resolves https://github.com/rust-lang/rust-analyzer/issues/15595. This change kinda approaches canonicalization—which I am not a fan of—but only in service of making `./`-configured commands run correctly.
Longer-term, I feel like this code should be removed once `rustfmt` supports recursive searches of configuration files or interpolation of values like `${workspace_folder}` lands in rust-analyzer.
## Testing
I cloned `rustc`, setup rust-analyzer as suggested in the [`rustc` dev guide](https://rustc-dev-guide.rust-lang.org/building/suggested.html#configuring-rust-analyzer-for-rustc), saved and formatted files in `src/tools/miri` and `compiler`, and saw `rustfmt` (seemingly) correctly.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions