diff options
| author | bors <bors@rust-lang.org> | 2023-08-30 19:51:32 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-08-30 19:51:32 +0000 |
| commit | 3da21b089ffe8337142fc054d3230749a304d832 (patch) | |
| tree | 53258de55f12309a8282967013cf8ed2a779ba09 /compiler/rustc_mir_transform/src/coverage/debug.rs | |
| parent | b97eaab558bd37f665b10a79fd5aecea3dde920f (diff) | |
| parent | 33cc140f55e254c7c88e81b059afcc430bba3e5e (diff) | |
| download | rust-3da21b089ffe8337142fc054d3230749a304d832.tar.gz rust-3da21b089ffe8337142fc054d3230749a304d832.zip | |
Auto merge of #11396 - y21:issue11345, r=Jarcho
new lint: `iter_out_of_bounds` Closes #11345 The original idea in the linked issue seemed to be just about arrays afaict, but I extended this to catch some other iterator sources such as `iter::once` or `iter::empty`. I'm not entirely sure if this name makes a lot of sense now that it's not just about arrays anymore (specifically, not sure if you can call `.take(1)` on an `iter::Empty` to be "out of bounds"?). changelog: [`iter_out_of_bounds`]: new lint
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/debug.rs')
0 files changed, 0 insertions, 0 deletions