Lint for Unnecessary Manual Bounds Checking

I ran across a section of translated C code that was written as such to manually avoid accessing a value out of bounds and returning a default value if it is out of bounds:

let hash_value = if pos + ZOPFLI_MIN_MATCH <= array.len() {
    array[pos + ZOPFLI_MIN_MATCH - 1]
} else {
    0
};

However, it would be better to detect this behaviour and recommend the following:

let hash_value = array.iter().nth(pos + ZOPFLI_MIN_MATCH - 1).cloned().unwrap_or(0);

Or even the following for more complicated mapping.

let hash_value = array.iter().nth(pos + ZOPFLI_MIN_MATCH - 1).map_or(0, |value| *value);

Start with the two Rust examples in the issue and inspect rust-clippy's existing lint entry points for bounds-checking patterns. Define the matching cases and verify that the lint recommends the iterator-based alternatives shown; the issue names no source file or test, so the appropriate locations must first be found in the repository.