SE-0302 (second review): Sendable and sendable closures

Thanks for asking. This @unchecked feature is ancillary syntactic sugar to what it’s being proposed. Given Swift’s high bar for syntactic sugar I was somewhat surprised this (in my view) single use case compiler feature is now part of the public user API. It makes Swift unnecessary a little more complex IMO which is not sustainable on the long run.