Clippy lints / Correctness
Clippy lint · Correctness · checked with Clippy 0.1.99
clippy::invalid_regex: Checks regex creation (with Regex::new, RegexBuilder::new, or RegexSet::new) for correct regex syntax
What it meansChecks regex creation (with Regex::new, RegexBuilder::new, or RegexSet::new) for correct regex syntax. It is in the correctness group and denied by default (the build fails).
Does it matter?
This will lead to a runtime panic.
Code that is almost certainly wrong. Denied by default: the build fails until you fix it or allow it.
How to fix it
Clippy does not fix this one automatically. Change the code by hand:
Flagged
Regex::new("(")
Write this instead
Regex::new("\(")
Turn it off, or on
Allow it where it does not fit your code, as narrowly as you can:
On one item
#[allow(clippy::invalid_regex)]
fn my_function() { /* ... */ }Whole crate (Cargo.toml)
[lints.clippy]
invalid_regex = "allow"One run
cargo clippy -- -A clippy::invalid-regexThe [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 regex creation
(with Regex::new, RegexBuilder::new, or RegexSet::new) for correct
regex syntax.
Why is this bad?
This will lead to a runtime panic.
Example
Regex::new("(")
Use instead:
Regex::new("\(")
From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.
Related lints
- infinite_iterinfinite iteration detected
- inherent_to_string_shadow_displaytype `main::A` implements inherent method `to_string(&self) -> String` which shadows the implementation of `Display`
- inline_fn_without_bodyuse of `#[inline]` on trait method `name` which has no body
- inverted_saturating_subinverted arithmetic check before subtraction
- invisible_charactersChecks for invisible Unicode characters in the code
- iter_next_loopChecks for loops on x.next()
All 847 Clippy lints · Rust compiler errors · Cargo.toml checker
Up next
Related lintclippy::infinite_iterinfinite iteration detectedRead it next →Did this answer your question?