Joe Groff
@bsneed @colincornaby It doesn't affect end users at all. The frameworks aren't going to spontaneously rewrite themselves in Swift.
-
@jckarter I don’t understand why you have to support bugs (rather than the promised contract) forever. Why not warn like with deprecation?
Michael Tsai
Peter Steinberger
Friedrich Markgraf
@mjtsai If subclassing is part of that contract, you have a lot more compatibility surface area to ensure subclassers don't break.
-
-
@jckarter I mean in general—undocumented/unpromised subclassing details and non-subclassing-related bugs. - View other replies
-
@mjtsai That's more important than technically-correct framework bug fixes or refactorings in a lot of cases. -
-
- View other replies
-
@concreteniche@mjtsai I think it'll lead to a more robust third-party framework ecosystem, whatever Apple ends up doing. -
@jckarter If this is about 3rd party frameworks, the vendor can always put a breaking change in a new version. If necessary to reverse a -
@jckarter bad decision. Whereas the framework client, without the ability to override, has no recourse. -
- View other replies
- Show more
-
Patrick Smith
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.