[swift-evolution] SE-0025: Scoped Access Level, next steps
panajev at gmail.com
Tue Mar 15 04:53:07 CDT 2016
I agree with you Tino that we should not stop here, but I would break it down in smaller proposals that had the biggest breakage in the language but still could all fit into Swift 3. It is one of the last chances of being allowed to break source and ABI compatibility and we ought to make it count IMHO.
Sent from my iPhone
> On 15 Mar 2016, at 09:45, Tino Heth via swift-evolution <swift-evolution at swift.org> wrote:
> I agree that the current "private" is useful, and would rather keep everything as-is than remove this scope.
> I'm neutral on adding a new access level, but don't like the "private(file)"-syntax:
> The issues with properties could be solved (my preference would be "private <file> (set) var x: Int"), but imho all access levels should be specified in the same way (that would put me in the "local" camp).
> If the access model is changed, i vote for a broad discussion about the topic as whole to minimize breaking changes (for example, it would be nice to have an elegant way to express that a method can be overridden by a subclass, but not be called).
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution