Colin Cornaby
But seriously, my favorite thing about Obj-C is it's a language for getting work done and complicated language semantics. Don't ruin that.
-
@bsneed@colincornaby It doesn't affect end users at all. The frameworks aren't going to spontaneously rewrite themselves in Swift.
Joe Groff
Dr. Sneed
Michael Tsai@jckarter @bsneed @colincornaby If it truly “doesn’t affect end users at all,” what could be the point of the change?
-
- View other replies
-
@jckarter Right, but presumably you expect that to ultimately benefit end users (indirectly). - View other replies
-
@mjtsai Users who are third-party framework devs I expect will benefit the most. - View other replies
-
@jckarter You’re saying no change for Apple Swift frameworks because you consider the API, but it’s about protecting others who don’t? - View other replies
-
@mjtsai Many users would prematurely reach for 'final' to get a similar effect and be stuck with it w/o the new default behavior. -
@jckarter I would have thought you could revoke a final across a module boundary because clients can’t inline, anyway. -
@mjtsai 'final' also influences things like dynamic casts and protocol conformance. e.g. Don't need to be covariant if there's no subtyping. -
@jckarter Aha, that makes sense. So then you either force a recompile or can’t optimize.
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.