[swift-evolution] SE-0025: Scoped Access Level, next steps

Jean-Daniel Dupas mailing at xenonium.com
Sun Mar 20 08:02:43 CDT 2016

> Le 19 mars 2016 à 15:35, Dany St-Amant via swift-evolution <swift-evolution at swift.org> a écrit :
>> Le 15 mars 2016 à 09:07, Ilya Belenkiy via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> a écrit :
>> These names are very uniform, and the context is immediately clear, but they are very long. The 2 most commonly used (and spelled out) would be access(global) and access(scope), public and private are much shorter and are well established terms of art.
> An option which goes against Swift being as explicit as possible is to support abbreviated scope, in addition to the full name:
> access(g)
> access(m)
> access(f)
> access(s)

Even knowing about what we are talking about, I got a hard time understanding what each option means.
Using single letter name is utterly confusing and unreadable.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160320/90af7a79/attachment.html>

More information about the swift-evolution mailing list