[flake8-type-checking] Clarify import cycle wording for TC001/TC002/TC003 (#24322)

Redovo1 · red · web-flow · commit da7b95893f39 · 2026-04-02T14:00:31.000Z
Co-authored-by: red &lt;red@reddeMacBook-Pro.local&gt;
diff --git a/crates/ruff_linter/src/rules/flake8_type_checking/rules/typing_only_runtime_import.rs b/crates/ruff_linter/src/rules/flake8_type_checking/rules/typing_only_runtime_import.rs
@@ -23,10 +23,11 @@ use crate::{Fix, FixAvailability, Violation};
 /// aren't defined in a type-checking block.
 ///
 /// ## Why is this bad?
-/// Unused imports add a performance overhead at runtime, and risk creating
-/// import cycles. If an import is _only_ used in typing-only contexts, it can
-/// instead be imported conditionally under an `if TYPE_CHECKING:` block to
-/// minimize runtime overhead.
+/// Imports that are only used for type annotations add a performance overhead
+/// at runtime. For first-party imports, they can also contribute to import
+/// cycles. If an import is _only_ used in typing-only contexts, it can instead
+/// be imported conditionally under an `if TYPE_CHECKING:` block to minimize
+/// runtime overhead.
 ///
 /// If [`lint.flake8-type-checking.quote-annotations`] is set to `true`,
 /// annotations will be wrapped in quotes if doing so would enable the
@@ -107,8 +108,8 @@ impl Violation for TypingOnlyFirstPartyImport {
 /// aren't defined in a type-checking block.
 ///
 /// ## Why is this bad?
-/// Unused imports add a performance overhead at runtime, and risk creating
-/// import cycles. If an import is _only_ used in typing-only contexts, it can
+/// Imports that are only used for type annotations add a performance overhead
+/// at runtime. If an import is _only_ used in typing-only contexts, it can
 /// instead be imported conditionally under an `if TYPE_CHECKING:` block to
 /// minimize runtime overhead.
 ///
@@ -190,8 +191,8 @@ impl Violation for TypingOnlyThirdPartyImport {
 /// annotations, but aren't defined in a type-checking block.
 ///
 /// ## Why is this bad?
-/// Unused imports add a performance overhead at runtime, and risk creating
-/// import cycles. If an import is _only_ used in typing-only contexts, it can
+/// Imports that are only used for type annotations add a performance overhead
+/// at runtime. If an import is _only_ used in typing-only contexts, it can
 /// instead be imported conditionally under an `if TYPE_CHECKING:` block to
 /// minimize runtime overhead.
 ///
