[swift-evolution] [Review] SE-0117: Default classes to be non-subclassable publicly

L. Mihalkovic laurent.mihalkovic at gmail.com
Wed Jul 6 12:24:23 CDT 2016

(From mobile)

> On Jul 6, 2016, at 7:52 AM, Chris Lattner via swift-evolution <swift-evolution at swift.org> wrote:
>> On Jul 5, 2016, at 5:54 PM, Kevin Lundberg via swift-evolution <swift-evolution at swift.org> wrote:
>> * What is your evaluation of the proposal?
>> -1 as is. I do not want to be constrained by authors of libraries or
>> frameworks into interacting with a system in only the ways they forsee.
>> By making the default be non-subclassable, if a designer does not put
>> thought into all the ways a class can be used then I as a consumer of
>> the library am penalized.
> Out of curiosity, what is your feeling about “internal” as the default level of access control?  It seems that following your concern to its logical conclusion would lead to a design where all members of a public class would be forced to be public.  After all, the author of a library or framework may not forsee the need to interact with a member that they did not explicitly mark public

Can't really help for feel like it is training wheels all around... or padlocks on every kitchen cupboards. What if this had been the philosophy from swift 0.1, what would the ecosystem look like today? (genuine question to which I do not have the answer)

> -Chris
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

More information about the swift-evolution mailing list