Clippy lints / Complexity
Clippy lint · Complexity · checked with Clippy 0.1.99
clippy::vec_box: `Vec<T>` is already on the heap, the boxing is unnecessary
What it meansChecks for usage of Vec<Box<T>> where T: Sized anywhere in the code. Check the Box documentation for more information. It is in the complexity group and warns by default.
What you see
warning: `Vec<T>` is already on the heap, the boxing is unnecessary --> main.rs:4:13 | 4 | values: Vec<Box<i32>>, | ^^^^^^^^^^^^^ help: try: `Vec<i32>` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#vec_box = note: `#[warn(clippy::vec_box)]` on by default
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?
Vec already keeps its contents in a separate area on the heap. So if you Box its contents, you just add another level of indirection.
Code that does something simple in a complicated way. Warns by default.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
struct X {
values: Vec<Box<i32>>,
}
Write this instead
struct X {
values: Vec<i32>,
}
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::vec_box)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
vec_box = "allow"One run
cargo clippy -- -A clippy::vec-boxThe [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
avoid-breaking-exported-api: Suppress lints whenever the suggested change would cause breakage for other crates.vec-box-size-threshold: The size of the boxed type in bytes, where boxing in a Vec is allowed
Clippy's own documentation
What it does
Checks for usage of Vec<Box<T>> where T: Sized anywhere in the code.
Check the Box documentation for more information.
Why is this bad?
Vec already keeps its contents in a separate area on
the heap. So if you Box its contents, you just add another level of indirection.
Example
struct X {
values: Vec<Box<i32>>,
}
Better:
struct X {
values: Vec<i32>,
}
Configuration
-
avoid-breaking-exported-api: Suppress lints whenever the suggested change would cause breakage for other crates.(default:
true) -
vec-box-size-threshold: The size of the boxed type in bytes, where boxing in aVecis allowed(default:
4096)
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- too_many_argumentsChecks for functions with too many parameters
- clone_on_copyusing `clone` on type `u64` which implements the `Copy` trait
- type_complexityChecks for types used in structs, parameters and let declarations above a certain complexity threshold
- useless_formatuseless use of `format!`
- useless_nonzero_new_unchecked`NonZeroUsize::new()` and `Option::unwrap()` can be safely used in a `const` context
- useless_transmuteChecks for transmutes to the original type of the object and transmutes that could be a cast
- while_let_loopthis loop could be written as a `while let` loop
- wildcard_in_or_patternsChecks for wildcard pattern used with others patterns in same match arm
- zero_divided_by_zeroconstant division of `0.0` with `0.0` will always result in NaN
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::too_many_argumentsChecks for functions with too many parametersRead it next →Did this answer your question?