Email me

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-box

The [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
Complexitygroup
warndefault level
nofixed by cargo clippy --fix
1.33.0added in Rust

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 a Vec is 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

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?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ