diff options
| author | bors <bors@rust-lang.org> | 2024-01-16 06:26:29 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-01-16 06:26:29 +0000 |
| commit | ecb0311fccae4d26ea448a61298b3ae6ffe233be (patch) | |
| tree | 780e139005961788f948b3b987d0d66583fc8705 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 771a2a965c300f91400f341d831797c3c41705a9 (diff) | |
| parent | 874f851ac5d82a5e2c68e46ddf850b8047f40415 (diff) | |
| download | rust-ecb0311fccae4d26ea448a61298b3ae6ffe233be.tar.gz rust-ecb0311fccae4d26ea448a61298b3ae6ffe233be.zip | |
Auto merge of #12149 - GuillaumeGomez:core-std-suggestions, r=llogiq
Correctly suggest std or core path depending if this is a `no_std` crate A few lints emit suggestions using `std` paths whether or not this is a `no_std` crate, which is an issue when running `rustfix` afterwards. So in case this is an item that is defined in both `std` and `core`, we need to check if the crate is `no_std` to emit the right path. r? `@llogiq` changelog: Correctly suggest std or core path depending if this is a `no_std` crate
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions