|
13 | 13 | /// A type whose values can safely be passed across concurrency domains by copying. |
14 | 14 | /// |
15 | 15 | /// You can safely pass values of a sendable type |
16 | | -/// from one concurrency domains to another --- |
| 16 | +/// from one concurrency domain to another --- |
17 | 17 | /// for example, you can pass a sendable value as the argument |
18 | 18 | /// when calling an actor's methods. |
19 | 19 | /// All of the following can be marked as sendable: |
|
24 | 24 | /// |
25 | 25 | /// - Reference types that internally manage access to their state |
26 | 26 | /// |
27 | | -/// - Functions and closures (via `@Sendable`) |
| 27 | +/// - Functions and closures (by marking them with `@Sendable`) |
28 | 28 | /// |
29 | 29 | /// Although this protocol doesn't have any required methods or properties, |
30 | 30 | /// it does have semantic requirements that are enforced at compile time. |
|
61 | 61 | /// Otherwise, you need to declare conformance to `Sendable` explicitly. |
62 | 62 | /// |
63 | 63 | /// Structures that have nonsendable stored properties |
64 | | -/// and enumerations that nonsendable associated values |
| 64 | +/// and enumerations that have nonsendable associated values |
65 | 65 | /// can be marked as `@unchecked Sendable`, |
66 | 66 | /// disabling compile-time correctness checks, |
67 | 67 | /// after you manually verify that |
|
103 | 103 | /// and the captured values must be of a sendable type. |
104 | 104 | /// |
105 | 105 | /// In a context that expects a sendable closure, |
106 | | -/// a closure closure that satisfies the requirements |
| 106 | +/// a closure that satisfies the requirements |
107 | 107 | /// implicitly conforms to `Sendable` --- |
108 | 108 | /// for example, in a call to `Task.detached(priority:operation:)`. |
109 | 109 | /// |
|
0 commit comments