Thanks for great talk. After seeing some of the code examples I strongly feel like strict concurrency in swift 6 needs more work. It is hard to reason about the code just by reading it. It is not really good to add #isolation just because compiler is throwing some error at me. It should be clearly visible to the programmer why it must be there, and not just compile and fix the 'errors' that programmer didn't anticipated just to shut up compiler error, without even realizing why it is happening and how added code fixed it. This is why I think this feature will not be widely adopted, simply because it is hard to read and not predictable enough. Story about await/async was to produce nice linear readable code that is easy to reason about. This goes opposite direction. (at least for now)
Great talk and plenty to learn. Thank you and hope you’ll do more talks.
Really great talk!
Thanks for great talk. After seeing some of the code examples I strongly feel like strict concurrency in swift 6 needs more work. It is hard to reason about the code just by reading it. It is not really good to add #isolation just because compiler is throwing some error at me. It should be clearly visible to the programmer why it must be there, and not just compile and fix the 'errors' that programmer didn't anticipated just to shut up compiler error, without even realizing why it is happening and how added code fixed it. This is why I think this feature will not be widely adopted, simply because it is hard to read and not predictable enough. Story about await/async was to produce nice linear readable code that is easy to reason about. This goes opposite direction. (at least for now)
YEssssss!