Skip to content

Commit 1baeaa8

Browse files
committed
Improve readability for implementing types definition restrictions
1 parent 4f298c9 commit 1baeaa8

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

src/items/implementations.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,8 @@ The associated item has a path of a path to the implementing type followed by
2424
the associate item's path component. Inherent implementations cannot contain
2525
associated type aliases.
2626

27-
A type can also have multiple inherent implementations but the implementing type
28-
must be defined within the same crate.
27+
A type can also have multiple inherent implementations. An implementing type
28+
must be defined within the same crate as the original type definition.
2929

3030
```rust
3131
struct Point {x: i32, y: i32}
@@ -45,6 +45,7 @@ my_point.log();
4545
A _trait implementation_ is defined like an inherent implementation except that
4646
the optional generic type declarations is followed by a [trait] followed
4747
by the keyword `for`. Followed by a path to a nominal type.
48+
4849
<!-- To understand this, you have to back-reference to the previous section. :( -->
4950

5051
The trait is known as the _implemented trait_. The implementing type

0 commit comments

Comments
 (0)