Clippy lints / Nursery
Clippy lint · Nursery · checked with Clippy 0.1.99
clippy::tuple_array_conversions: it looks like you're trying to convert a tuple to an array
What it meansChecks for tuple<=>array conversions that are not done with .into(). It is in the nursery group and off by default.
What you see
warning: it looks like you're trying to convert a tuple to an array --> main.rs:4:49 | 4 | let v1: Vec<[u32; 2]> = t1.iter().map(|&(a, b)| [a, b]).collect(); | ^^^^^^ | = help: use `.into()` instead, or `<[T; N]>::from` if type annotations are needed = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#tuple_array_conversions = note: `-W clippy::tuple-array-conversions` implied by `-W clippy::nursery`
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?
It may be unnecessary complexity. .into() works for converting tuples<=> arrays of up to 12 elements and conveys the intent more clearly, while also leaving less room for hard to spot bugs!
New lints still being finished. Off by default and may have false positives.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
let t1 = &[(1, 2), (3, 4)];
let v1: Vec<[u32; 2]> = t1.iter().map(|&(a, b)| [a, b]).collect();
Write this instead
let t1 = &[(1, 2), (3, 4)];
let v1: Vec<[u32; 2]> = t1.iter().map(|&t| t.into()).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]
tuple_array_conversions = "warn"In code
#![warn(clippy::tuple_array_conversions)]One run
cargo clippy -- -W clippy::tuple-array-conversionsThe [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.
Settings in clippy.toml
msrv: The minimum rust version that the project supports. Defaults to the rust-version field in Cargo.toml
Clippy's own documentation
What it does
Checks for tuple<=>array conversions that are not done with .into().
Why is this bad?
It may be unnecessary complexity. .into() works for converting tuples<=> arrays of up to
12 elements and conveys the intent more clearly, while also leaving less room for hard to
spot bugs!
Known issues
The suggested code may hide potential asymmetry in some cases. See #11085 for more info.
Example
let t1 = &[(1, 2), (3, 4)];
let v1: Vec<[u32; 2]> = t1.iter().map(|&(a, b)| [a, b]).collect();
Use instead:
let t1 = &[(1, 2), (3, 4)];
let v1: Vec<[u32; 2]> = t1.iter().map(|&t| t.into()).collect();
Configuration
-
msrv: The minimum rust version that the project supports. Defaults to therust-versionfield inCargo.toml(default:
current version)
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- redundant_cloneChecks for a redundant clone() (and its relatives) which clones an owned value that is going to be dropped without further use
- trait_duplication_in_boundsthis trait bound is already specified in the where clause
- transmute_undefined_reprtransmute from `main::Foo<u32>` to `main::Foo<i32>`, both of which have an undefined layout
- trivial_regexChecks for trivial regex creation (with Regex::new, RegexBuilder::new, or RegexSet::new)
- type_repetition_in_boundstype `T` has already been used as a bound predicate
- uninhabited_referencesdereferencing a reference to an uninhabited type would be undefined behavior
- unnecessary_struct_initializationunnecessary struct building
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::redundant_cloneChecks for a redundant clone() (and its relatives) which clones an owned value that is going to be dropped without further useRead it next →Did this answer your question?