Clippy · Correctness

assume_init on uninitialized MaybeUninit memory

clippy::uninit_assumed_init

Initialize the value, or keep it as MaybeUninit until every byte is written.

Category: Correctness
Default level: warn
Tier: P1
Producer: Clippy
Diff scope: line

Not a defect when

The assumed type consists only of MaybeUninit values, such as [MaybeUninit<T>; N], which is valid while uninitialized and is the documented idiom for building an array element by element.

What it reads

Clippy, with the compiler behind it. The only pass that compiles.

Tier

Serious: worth interrupting other work for.

The tier bounds how severe a rule may be; its category bounds the tier.

Diff scope

The changed line itself.

What --scope contextual looks at to decide whether a change caused the finding.

Change it

Turn it off, or make it blocking, without touching the code it flags:

rust-doctor --rule clippy::uninit_assumed_init=off .
rust-doctor --rule clippy::uninit_assumed_init=error .

Set it once in rust-doctor.toml

Upstream