Clippy lints / Correctness
Clippy lint · Correctness · checked with Clippy 0.1.99
clippy::invisible_characters: Checks for invisible Unicode characters in the code
What it meansChecks for invisible Unicode characters in the code. It is in the correctness group and denied by default (the build fails).
Does it matter?
Having an invisible character in the code makes for all sorts of April fools, but otherwise is very much frowned upon.
Code that is almost certainly wrong. Denied by default: the build fails until you fix it or allow it.
How to fix it
Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::invisible_characters)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
invisible_characters = "allow"One run
cargo clippy -- -A clippy::invisible-charactersThe [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 invisible Unicode characters in the code.
Why is this bad?
Having an invisible character in the code makes for all sorts of April fools, but otherwise is very much frowned upon.
Example
You don’t see it, but there may be a zero-width space or soft hyphen somewhere in this text.
Past names
- zero_width_space
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- inline_fn_without_bodyuse of `#[inline]` on trait method `name` which has no body
- invalid_regexChecks regex creation (with Regex::new, RegexBuilder::new, or RegexSet::new) for correct regex syntax
- inverted_saturating_subinverted arithmetic check before subtraction
- iter_next_loopChecks for loops on x.next()
- iter_skip_zerousage of `.skip(0)`
- iterator_step_by_zero`Iterator::step_by(0)` will panic at runtime
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::inline_fn_without_bodyuse of `#[inline]` on trait method `name` which has no bodyRead it next →Did this answer your question?