FWIW, you're not the first to propose these names. `public(open)` was suggested during the `open` debate and rejected in favor of `open`. `private(file)` was suggested during the `fileprivate` debate and rejected in favor of `fileprivate`. `protected` and `abstract` have been suggested on this list multiple times.
On Mon, Feb 13, 2017 at 12:04 AM, Vanderlei Martinelli via swift-evolution < swift-evolution@swift.org> wrote: > Some corrections and additions to my previous email: > > public(open) // if open is absent, the method is “closed” > protected // (yes, we and Cocoa still use classes) > internal > private(file) // if file is absent, the method is really, really private > > And one observation: protected and abstract as described before: only > to be valid for classes, of course. Something like local access modifier > for local only scope would be nice too (and does not break anything written > until today). > > — > Vanderlei Martinelli > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution > >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
