diff options
| author | bors <bors@rust-lang.org> | 2024-07-02 15:17:47 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-07-02 15:17:47 +0000 |
| commit | 6e6683b15ee32fd875ff682d7c9c35b7a61c5151 (patch) | |
| tree | dcb45f7ae65b4c440558d535303e84bba2bbde86 /compiler/rustc_codegen_gcc | |
| parent | c4f81d00a28d67c35b82fc3c21619a6228de498b (diff) | |
| parent | 0dd8b27b6b44533357848276e190f684cb36b797 (diff) | |
| download | rust-6e6683b15ee32fd875ff682d7c9c35b7a61c5151.tar.gz rust-6e6683b15ee32fd875ff682d7c9c35b7a61c5151.zip | |
Auto merge of #13030 - astra-90:master, r=Alexendoo
Fix #12964 - false positive with `into_iter_without_iter` changelog: FP: `into_iter_without_iter`: No longer lints when the `iter` or `iter_mut` implementation is not within the first `impl` block fixes #12964 --- I'm pretty new to this open-source thing, so hopefully I did everything right. Got a little annoyed this false positive was happening in my code and the issue was inactive for two weeks so I thought I'd fix it myself. As an aside, maybe `iter.map(...).next()` could be linted against? I don't see that ever being preferred over `iter.next().map(...)`, and it could've prevented the bug here.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions