[swift-evolution] final + lazy + fileprivate modifiers
Jose Cheyo Jimenez
cheyo at masters3d.com
Fri Feb 17 18:52:27 CST 2017
> Relative to Swift 3, the bar for such changes is significantly higher:
> The existing syntax/API being changed must be actively harmful.
> The new syntax/API must clearly be better and not conflict with existing Swift syntax.
> There must be a reasonably automatable migration path for existing code.
I don’t think there is evidence that scope private in Swift3 is "actively harmful”.
Reverting to Swift2 file-private as private is not clearly better.
The community has not converged on a clear winner.
The only positive thing here is that if we get rid of scope private then it will be easy to make private alias to file-private so no code will break, but we would be removing a feature so I would think this is a breaking change.
Would removing private and fileprivate by making them alias to internal also be a breaking change? Even if the code will still compile?
This is a linter problem. If people don’t want other people in their team to use scope private then make it part of the coding style.
If people do not want fileprivate because it looks ugly, then force everybody to use scope private using a linter like swiftlint.
> On Feb 17, 2017, at 2:35 PM, Matthew Johnson via swift-evolution <swift-evolution at swift.org> wrote:
>> On Feb 17, 2017, at 4:29 PM, Brent Royal-Gordon via swift-evolution <swift-evolution at swift.org> wrote:
>>> 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.
> +1. I’d like to see `private` revert to the Swift 2 meaning, and hopefully we can reconsider using `scoped` as the keyword for scoped access rather than abandoning it. Does anyone remember why this was considered a bad idea?
>> Brent Royal-Gordon
>> swift-evolution mailing list
>> swift-evolution at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution