From fb406a2e50761f0f1f2fa60d63cce3df47440c69 Mon Sep 17 00:00:00 2001 From: Imbris <2002109+Imberflur@users.noreply.github.com> Date: Thu, 14 Aug 2025 11:01:26 -0400 Subject: [PATCH] Fix example in orphan rule rationale --- src/items/implementations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/items/implementations.md b/src/items/implementations.md index 0c5ec6652..91ebca318 100644 --- a/src/items/implementations.md +++ b/src/items/implementations.md @@ -178,7 +178,7 @@ The *orphan rule* states that a trait implementation is only allowed if either t An orphan implementation is one that implements a foreign trait for a foreign type. If these were freely allowed, two crates could implement the same trait for the same type in incompatible ways, creating a situation where adding or updating a dependency could break compilation due to conflicting implementations. -The orphan rule enables library authors to add new implementations to their traits without fear that they'll break downstream code. Without these restrictions, a library couldn't add an implementation like `impl MyTrait for T` without potentially conflicting with downstream implementations. +The orphan rule enables library authors to add new implementations to their traits without fear that they'll break downstream code. Without these restrictions, a library couldn't add an implementation like `impl Trait for LocalGenericType` without potentially conflicting with downstream implementations. r[items.impl.trait.orphan-rule.general] Given `impl Trait for T0`, an `impl` is valid only if at