Skip to content

Add: orphan rule rationale. #1755

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 3, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix: grammar error . Fix: improved semantics
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
  • Loading branch information
TmSalviano and joshtriplett authored Mar 13, 2025
commit 009ebdde96196b1a701e470d32c53e7b91e19e6f
2 changes: 1 addition & 1 deletion src/items/implementations.md
Original file line number Diff line number Diff line change
Expand Up @@ -175,7 +175,7 @@ r[items.impl.trait.orphan-rule]
#### Orphan rules

r[items.impl.trait.orphan-rule.rationale]
The orphan rules ensure that other peoples code can't break your code, and vice versa.
The orphan rule helps ensure that other people's code can't break your code, and vice versa.
If an external crate implements an external trait for an external type, and your crate also
implements the same trait for the same type, the compiler wouldn't know which implementation
to use.\
Expand Down