Documentation

Author: MichaReiser

crates/ruff_linter/src/rules/pylint/mod.rs

@@ -441,7 +441,6 @@ mod tests {
         Ok(())
     }
 
-
     #[test_case(Rule::BadStrStripCall, Path::new("bad_str_strip_call.py"))]
     fn preview_rules(rule_code: Rule, path: &Path) -> Result<()> {
         let snapshot = format!(

crates/ruff_linter/src/rules/pylint/rules/repeated_equality_comparison.rs

@@ -18,6 +18,10 @@ use crate::Locator;
 /// Checks for repeated equality comparisons that can be rewritten as a membership
 /// test.
 ///
+/// This rule will try to determine if the values are hashable
+/// and the fix will use a `set` if they are. If unable to determine, the fix
+/// will use a `tuple` and suggest the use of a `set`.
+///
 /// ## Why is this bad?
 /// To check if a variable is equal to one of many values, it is common to
 /// write a series of equality comparisons (e.g.,
@@ -28,10 +32,6 @@ use crate::Locator;
 /// If the items are hashable, use a `set` for efficiency; otherwise, use a
 /// `tuple`.
 ///
-/// This rule will try to determine if the values are hashable
-/// and the fix will use a `set` if they are. If unable to determine, the fix
-/// will use a `tuple` and continue to suggest the use of a `set`.
-///
 /// ## Example
 /// ```python
 /// foo == "bar" or foo == "baz" or foo == "qux"