Clippy lints / Style
Clippy lint · Style · checked with Clippy 0.1.99
clippy::bytes_nth: called `.bytes().nth()` on a `str`
What it meansChecks for the use of .bytes().nth(). It is in the style group and warns by default.
What you see
warning: called `.bytes().nth()` on a `str` --> main.rs:3:1 | 3 | "Hello".bytes().nth(3); | ^^^^^^^^^^^^^^^^^^^^^^ help: try: `"Hello".as_bytes().get(3).copied()` | = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#bytes_nth = note: `#[warn(clippy::bytes_nth)]` 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?
.as_bytes().get() is more efficient and more readable.
Code that works but is not idiomatic Rust. Warns by default.
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.
Flagged
"Hello".bytes().nth(3);
Write this instead
"Hello".as_bytes().get(3);
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::bytes_nth)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
bytes_nth = "allow"One run
cargo clippy -- -A clippy::bytes-nthThe [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 the use of .bytes().nth().
Why is this bad?
.as_bytes().get() is more efficient and more
readable.
Example
"Hello".bytes().nth(3);
Use instead:
"Hello".as_bytes().get(3);
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- needless_returnunneeded `return` statement
- new_without_defaultChecks for public types with a pub fn new() -> Self method and no implementation of Default
- len_zeroChecks for getting the length of something via .len() just to compare to zero, and suggests using .is_empty() where applicable
- box_default`Box::new(_)` of default value
- builtin_type_shadowthis generic shadows the built-in type `u32`
- byte_char_slicescan be more succinctly written as a byte str
- chars_last_cmpChecks for usage of _.chars().last() or _.chars().next_back() on a str to check if it ends with a given char
- chars_next_cmpyou should use the `starts_with` method
- chunks_exact_to_as_chunksusing `chunks_exact` with a constant chunk size
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::needless_returnunneeded `return` statementRead it next →Did this answer your question?