Scott, I think your writing got a bit confuse but, if I got your intention right, since you are the owner of the class, you may choose to subclass it or not internally, no questions asked. I need no finals in my apps and I only subclass if I intend to. If you are in control of your own code, why would you need to ensure there would be no subclassing/overriding? I'm not opposed to keeping the keyword if it is important to anyone to be sure of that for internals. As for what is public you will gain better control of what other people do to your classes and methods.
L On 6 July 2016 at 16:56, Scott James Remnant <[email protected]> wrote: > >> On Jul 6, 2016, at 12:50 PM, Leonardo Pessoa <[email protected]> wrote: >> >> Scott, you really got a point here: should this proposal pass, I >> believe the final keyword should be removed as it would be already the >> default behaviour and thus unnecessary. I don't think this is on the >> proposal. >> > > Removing the `final` keyword would mean there would be no way to have a class > of `internal` (default) scope that subclasses and another class of `internal` > (default) scope and overrides a method of `internal` (default) scope. > > Scott > _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
