Generated by 🚫 Danger

This looks super cool! Thanks so much for doing it.

I didn't even think of the generic constraint case! There could be others, like the use of the sending keyword. I'm not exactly sure and it would take some experimenting to figure out. But this is wonderful regardless!

There could be others, like the use of the sending keyword. I'm not exactly sure and it would take some experimenting to figure out.

I've added checking for sending keywords. However, I think that it's not needed because of the statement about source compatibility in the introducing proposal:

In the Swift 5 language mode, sending diagnostics are suppressed under minimal concurrency checking, and diagnosed as warnings under strict concurrency checking. The diagnostics are errors in the Swift 6 language mode, as shown in the code examples in this proposal. This diagnostic behavior based on language mode allows sending to be adopted in existing Concurrency APIs including CheckedContinuation.

Would you agree, @mattmassicotte? I did some experiments as well and haven't seen any changes with or without @preconcurrency. That doesn't mean much, though, as I'm not sure whether my examples have been sufficient.

Yeah I wasn't sure about sending, parameters in particular. But that text does seem unambiguous, and the biggest culprits are global actors and @Sendable anyways. So I think this will provide very good coverage.

Thanks again for doing this, super cool!