Clippy lints / Complexity
Clippy lint · Complexity · checked with Clippy 0.1.99
clippy::useless_transmute: Checks for transmutes to the original type of the object and transmutes that could be a cast
What it meansChecks for transmutes to the original type of the object and transmutes that could be a cast. It is in the complexity group and warns by default.
Does it matter?
Readability. The code tricks people into thinking that something complex is going on.
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
core::intrinsics::transmute(t); // where the result type is the same as `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::useless_transmute)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
useless_transmute = "allow"One run
cargo clippy -- -A clippy::useless-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 to the original type of the object and transmutes that could be a cast.
Why is this bad?
Readability. The code tricks people into thinking that something complex is going on.
Example
core::intrinsics::transmute(t); // where the result type is the same as `t`'s
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_conversionuseless conversion to the same type: `std::string::String`
- useless_formatuseless use of `format!`
- useless_nonzero_new_unchecked`NonZeroUsize::new()` and `Option::unwrap()` can be safely used in a `const` context
- vec_box`Vec<T>` is already on the heap, the boxing is unnecessary
- 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
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?