Clippy lints / Suspicious
Clippy lint · Suspicious · checked with Clippy 0.1.99
clippy::crosspointer_transmute: Checks for transmutes between a type T and *T
What it meansChecks for transmutes between a type T and *T. It is in the suspicious group and warns by default.
Does it matter?
It’s easy to mistakenly transmute between a type and a pointer to that type.
Code that is most likely wrong or useless. Warns by default.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
core::intrinsics::transmute(t) // where the result type is the same as
// `*t` or `&t`'s
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::crosspointer_transmute)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
crosspointer_transmute = "allow"One run
cargo clippy -- -A clippy::crosspointer-transmuteThe [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 transmutes between a type T and *T.
Why is this bad?
It’s easy to mistakenly transmute between a type and a pointer to that type.
Example
core::intrinsics::transmute(t) // where the result type is the same as
// `*t` or `&t`'s
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- confusing_method_to_numeric_castcasting function pointer `u16::max` to `usize`
- const_is_emptythis expression always evaluates to true
- crate_in_macro_def`crate` references the macro call's crate
- declare_interior_mutable_constnamed constant with interior mutability
- deprecated_clippy_cfg_attr`feature = "cargo-clippy"` was replaced by `clippy`
- doc_nested_refdefslink reference defined in list item
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::confusing_method_to_numeric_castcasting function pointer `u16::max` to `usize`Read it next →Did this answer your question?