SE-0302: ConcurrentValue and @concurrent closures

Agree, I like this approach a lot for value types receiving a conformance in their base declaration. It's less clear to me how this would work for classes though. Would @sendable(unsafe) have to be applied to all mutable (and non-sendable constant) properties? One consequence of using that approach would be that immutable classes whose properties are all sendable would not require any unsafe annotation.

Some of this would be covered by SE-0293 (second review): Extend Property Wrappers to Function and Closure Parameters wouldn't it?