diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2025-01-27 21:36:12 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-27 21:36:12 +0000 |
| commit | 83bde363b633a68a1a94441b685ee5a87c60879c (patch) | |
| tree | 952d3c3067e5e2b206c99226a3ea78f8ba2e601d /compiler/rustc_mir_transform/src | |
| parent | 85bbba69b0d92a314a0751bcbdaa28e800625f61 (diff) | |
| parent | 3b0b8b080eedfeadc366c051d1c14307c7a7455e (diff) | |
| download | rust-83bde363b633a68a1a94441b685ee5a87c60879c.tar.gz rust-83bde363b633a68a1a94441b685ee5a87c60879c.zip | |
correct suggestions in `no_std` (#13999)
I opened https://github.com/rust-lang/rust-clippy/pull/13896 before. However, I found that there're more cases where Clippy suggests to use modules that belong to the `std` crate even in a `no_std` environment. Therefore, this PR include the changes I've made in #13896 and new changes to fix cases I found this time to prevent wrong suggestions in `no_std` environments as well. changelog: [`redundant_closure`]: correct suggestion in `no_std` changelog: [`repeat_vec_with_capacity`]: correct suggestion in `no_std` changelog: [`single_range_in_vec_init`]: don't emit suggestion to use `Vec` in `no_std` changelog: [`drain_collect`]: correct suggestion in `no_std` changelog: [`map_with_unused_argument_over_ranges`]: correct suggestion in `no_std` also close #13895
Diffstat (limited to 'compiler/rustc_mir_transform/src')
0 files changed, 0 insertions, 0 deletions