Skip to content

Commit 2dd624a

Browse files
authored
Clarify Copy linguistics
A type as *being* "Copy" as an adjective collides with the common sense word "copy" being either a verb or a noun. Something is a copy of, or you copy from something to something else. The documentation should (I feel) reflect this not to confuse readers (as I was). I'm not sure whether the "ˋCopyˋable" semantics is congruent with Rust traits, having no experience with it, but I think it adds to the readability of this section.
1 parent 2f04f65 commit 2dd624a

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

src/ch04-01-what-is-ownership.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -388,10 +388,13 @@ we add the `Copy` annotation to that type, we’ll get a compile-time error. To
388388
learn about how to add the `Copy` annotation to your type, see [“Derivable
389389
Traits”][derivable-traits]<!-- ignore --> in Appendix C.
390390

391-
So what types are `Copy`? You can check the documentation for the given type to
392-
be sure, but as a general rule, any group of simple scalar values can be
393-
`Copy`, and nothing that requires allocation or is some form of resource is
394-
`Copy`. Here are some of the types that are `Copy`:
391+
So what types are `Copy`able? You can check the documentation for the given type to
392+
be sure, but as a general rule:
393+
394+
1. Any group of simple scalar values can have the `Copy` trait,
395+
2. Nothing that requires allocation or is some form of resource is `Copy`able.
396+
397+
Here are some of the types that are `Copy`able:
395398

396399
* All the integer types, such as `u32`.
397400
* The Boolean type, `bool`, with values `true` and `false`.

0 commit comments

Comments
 (0)