Skip to content

Commit 891932e

Browse files
committed
Remove double wording in opaque type chapter
Fixes up some word soup I came across reading the chapter.
1 parent 5eb3cbd commit 891932e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/ffi.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -912,8 +912,8 @@ By including at least one private field and no constructor,
912912
we create an opaque type that we can't instantiate outside of this module.
913913
(A struct with no field could be instantiated by anyone.)
914914
We also want to use this type in FFI, so we have to add `#[repr(C)]`.
915-
The marker ensures the compiler does not mark the struct as `Send`, `Sync` and `Unpin` are
916-
not applied to the struct. (`*mut u8` is not `Send` or `Sync`, `PhantomPinned` is not `Unpin`)
915+
The marker ensures the compiler does not mark the struct as `Send`, `Sync`, and
916+
`Unpin`. (`*mut u8` is not `Send` or `Sync`, `PhantomPinned` is not `Unpin`)
917917

918918
But because our `Foo` and `Bar` types are
919919
different, we’ll get type safety between the two of them, so we cannot

0 commit comments

Comments
 (0)