I've generally been in favor of the "put protocol conformance in extensions" approach that @dimsumthinking advocates.
But chasing down "Main actor-isolated property '...' cannot be used to satisfy nonisolated protocol requirement" warnings, when you can't figure out what protocol is being referenced and it isn't done in this file? yeah… got me questioning myself on that.
=> More informations about this toot | More toots from cocoaphony@mastodon.social
@cocoaphony @dimsumthinking A) This sounds like potentially just poor diagnostics maybe?
B) do you never do the preconcurrency conformance thing just to make it work?
C) are you as excited for “isolated conformances” as I am from the vision doc?
=> More informations about this toot | More toots from mattiem@mastodon.social
@mattiem @dimsumthinking
A) If it told me the protocol it would certainly help a lot.
B) No
C) Yes. But in this case, I control all the pieces. It’s our protocol and our conformance. So I don’t think isolated conformances really apply.
1/
=> More informations about this toot | More toots from cocoaphony@mastodon.social
@mattiem @dimsumthinking
But I’m also not quite certain that isolated conformances will be as useful as we would hope.
Excited as I am for the vision (and I really am!) the words “SwiftUI” and “UIKit” never appear. So I don’t know how the vision will translate in terms of “works for iOS devs.” Will this vision help us with Combine? NotificationCenter? Hard to be sure. (Have you heard more explicit discussion about that?)
=> More informations about this toot | More toots from cocoaphony@mastodon.social
@cocoaphony @dimsumthinking I would really love to file bugs about poor diagnostics and note them in the forum thread asking about that. They have improved in 6.1, but there’s move work to do.
=> More informations about this toot | More toots from mattiem@mastodon.social
@mattiem @dimsumthinking Agreed. https://github.com/swiftlang/swift/issues/78518
=> More informations about this toot | More toots from cocoaphony@mastodon.social
text/gemini
This content has been proxied by September (3851b).