A type that conforms to Sendable type is a thread-safe type?

[hborla (Holly Borla)]

@shiz

For example, if a non-Sendable class which has a Sendable struct(e.g. Array<Int>) is accessed from multiple concurrent contexts at once and the class calls the struct's mutating func, data races could be caused.

In this scenario, the race that you'd get would be on the variable of the non-Sendable class, not the array value itself. I don't think the description in this proposal is incorrect, and I do think that programmers should think about types conforming to Sendable is being inherently thread-safe.