Joe Groff
@curtclifton @owensd Platform bugs suck and are inevitable, but there are other, more resilient ways to cope than monkey patching.
-
@mjtsai@jckarter@jaredsinclair@curtclifton@owensd I suspect that’ll happen coz the Swift-written framework should be usable from Obj-C.
Michael Tsai
Curt Clifton
JΛЯΣD
Roopesh Chander
@roopeshchander Eventually they’re going to want frameworks that take advantage of Swift features that don’t work with Objective-C.
-
-
@mjtsai Agreed. That may be a few decades in the future, but it’s better it’s discussed about now. -
@mjtsai OTOH, a Swift framework to be used only from Swift written decades later would most likely use POP => we can override the protocol -
@roopeshchander Pretty sure that’s less flexible, though I’m not super familiar with how protocols work under the hood. -
@mjtsai Protocol methods are always override-able, even if you assign a subtype to a protocl-type. Like in:http://nomothetis.svbtle.com/the-ghost-of-swift-bugs-future … - View other replies
-
@roopeshchander Yes, but only overridable within your code, right? -
@mjtsai If the protocol is public, it should be possible to override across modules (I’ve not tested this though). -
@mjtsai But, like I said, whenever there’s a final class in the hierarchy, it becomes unoverridable … - View other replies
-
@mjtsai … And many APIs will be made of classes/structs even in POP, so maybe my point is moot.
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.