[swift-evolution] final + lazy + fileprivate modifiers
brent at architechies.com
Fri Feb 17 16:29:57 CST 2017
> On Feb 17, 2017, at 12:29 AM, Slava Pestov via swift-evolution <swift-evolution at swift.org> wrote:
> Personally I feel enforced encapsulation of implementation detail to the latter group is less important than the former, and can be handled by convention. Whereas other users of your module definitely benefit from access control and being able to consume a clearly-defined interface.
I also think it's often helpful to be able to change a member's access level without having to change all references to it. Publishing or privatizing an interface is not an uncommon refactoring.
Not everybody likes our current semantics, but that's no reason to throw the feature out entirely.
More information about the swift-evolution