Daniel Jalkut
"Not all classes make sense to subclass." It's absurd to imagine you can predict all valid subclassing patterns. http://mjtsai.com/blog/2016/07/17/swift-classes-to-be-non-publicly-subclassable-by-default/ …
Paul Haddad
-
-
@tapbot_paul Sounds like the gist is to make Swift classes non-subclassable by default, but just debating the syntax for undoing that. - View other replies
-
@danielpunkass Can you give an example of why it shouldn't be allowed? Wondering about how it might affect future projects. -
@jonathanlace I'm a proponent of allowing it. Arguments against are many: for example a subclass can upset the expectations of the super. -
@danielpunkass This is just about what the default will be or at all? -
@jonathanlace The default. Framework designers (including in Apple) will have to go out of their way to make a class subclassable. -
@danielpunkass Something more than a keyword? -
@jonathanlace Nope, just a keyword. -
@danielpunkass I love the philosophical angle of debates like this. Which default is more logical? Some issues are interdisciplinary :) - Show more
-
-
-
@tapbot_paul The rejection cited here (https://lists.swift.org/pipermail/swift-evolution-announce/2016-July/000234.html …) seems to be only about the syntax of it.
-
Jonathan Lace
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.