From 403aa005a764799319f24f377698d17a5b96701d Mon Sep 17 00:00:00 2001 From: shiz <35151927+stzn@users.noreply.github.com> Date: Wed, 12 Jun 2024 16:09:10 +0900 Subject: [PATCH] fix the description that Sendable type is thread-safe type --- proposals/0430-transferring-parameters-and-results.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/proposals/0430-transferring-parameters-and-results.md b/proposals/0430-transferring-parameters-and-results.md index 6a973018c5..00b24714b6 100644 --- a/proposals/0430-transferring-parameters-and-results.md +++ b/proposals/0430-transferring-parameters-and-results.md @@ -157,9 +157,10 @@ public func withCheckedContinuation( ### Sendable Values and Sendable Types -A type that conforms to the `Sendable` protocol is a thread-safe type: values of -that type can be shared with and used safely from multiple concurrent contexts -at once without causing data races. If a value does not conform to `Sendable`, +A type that conforms to the `Sendable` protocol can be used safely from multiple +concurrent contexts at once without causing data races since values of +that type can be shared with in a thread-safe way or transferred by copying them +to avoid sharing. If a value does not conform to `Sendable`, Swift must ensure that the value is never used concurrently. The value can still be sent between concurrent contexts, but the send must be a complete transfer of the value's entire region implying that all uses of the value (and anything