Suggestion about the description that "A type that conforms to the Sendable
protocol is a thread-safe type"
#2482
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we talked about the above description, we thought that it's not correct since the type which conforms to
Sendable
is not always thread-safe.For example, if a non-
Sendable
class which has aSendable
struct(e.g.Array<Int>
) is accessed from multiple concurrent contexts at once and the class calls the struct'smutating
func, data races could be caused.We think that Swift just has a system to avoid data races rather than guaranteeing thread safety for types and it's better to change the description.
We are proposing an amendment. Please check it.
Thank you.
Discussion thread: https://forums.swift.org/t/a-type-that-conforms-to-sendable-type-is-a-thread-safe-type/72381