Clippy lints / Pedantic
Clippy lint · Pedantic · checked with Clippy 0.1.99
clippy::flat_map_option: used `flat_map` where `filter_map` could be used instead
What it meansChecks for usage of Iterator::flat_map() where filter_map() could be used instead. It is in the pedantic group and off by default.
What you see
warning: used `flat_map` where `filter_map` could be used instead --> main.rs:3:49 | 3 | let nums: Vec<i32> = ["1", "2", "whee!"].iter().flat_map(|x| x.parse().ok()).collect(); | ^^^^^^^^ help: try: `filter_map` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#flat_map_option = note: `-W clippy::flat-map-option` implied by `-W clippy::pedantic`
Real output of Clippy 0.1.99 (Rust 1.99) on the example below. Names and line numbers in yours will differ.
Does it matter?
filter_map() is known to always produce 0 or 1 output items per input item, rather than however many the inner iterator type produces. Therefore, it maintains the upper bound in Iterator::size_hint(), and communicates to the reader that the input items are not being expanded into multiple output items without their having to notice that the mapping function returns an Option.
Stricter lints with some false positives. Off by default; opt in with clippy::pedantic.
How to fix it
Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.
Flagged
let nums: Vec<i32> = ["1", "2", "whee!"].iter().flat_map(|x| x.parse().ok()).collect();
Write this instead
let nums: Vec<i32> = ["1", "2", "whee!"].iter().filter_map(|x| x.parse().ok()).collect();
Turn it off, or on
It is off by default. To use it, set it to warn or deny:
Whole crate (Cargo.toml)
[lints.clippy]
flat_map_option = "warn"In code
#![warn(clippy::flat_map_option)]One run
cargo clippy -- -W clippy::flat-map-optionThe [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.
Clippy's own documentation
What it does
Checks for usage of Iterator::flat_map() where filter_map() could be
used instead.
Why is this bad?
filter_map() is known to always produce 0 or 1 output items per input item,
rather than however many the inner iterator type produces.
Therefore, it maintains the upper bound in Iterator::size_hint(),
and communicates to the reader that the input items are not being expanded into
multiple output items without their having to notice that the mapping function
returns an Option.
Example
let nums: Vec<i32> = ["1", "2", "whee!"].iter().flat_map(|x| x.parse().ok()).collect();
Use instead:
let nums: Vec<i32> = ["1", "2", "whee!"].iter().filter_map(|x| x.parse().ok()).collect();
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- too_many_linesChecks for functions with a large amount of lines
- missing_errors_docChecks the doc comments of publicly visible functions that return a Result type and warns if there is no # Errors section
- must_use_candidateChecks for public functions that have no #[must_use] attribute, but return something not already marked must-use, have no mutable arg and mutate no statics
- explicit_into_iter_loopChecks for loops on y.into_iter() where y will do, and suggests the latter
- explicit_iter_loopChecks for loops on x.iter() where &x will do, and suggests the latter
- filter_map_nextcalled `filter_map(..).next()` on an `Iterator`
- float_cmpstrict comparison of `f32` or `f64`
- fn_params_excessive_boolsChecks for excessive use of bools in function declarations
- format_collectuse of `format!` to build up a string from an iterator
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::too_many_linesChecks for functions with a large amount of linesRead it next →Did this answer your question?