<html><head><style>
body {
font-family: "Helvetica Neue", Helvetica, Arial, sans-serif;
padding:1em;
margin:auto;
background:#fefefe;
}
h1, h2, h3, h4, h5, h6 {
font-weight: bold;
}
h1 {
color: #000000;
font-size: 28pt;
}
h2 {
border-bottom: 1px solid #CCCCCC;
color: #000000;
font-size: 24px;
}
h3 {
font-size: 18px;
}
h4 {
font-size: 16px;
}
h5 {
font-size: 14px;
}
h6 {
color: #777777;
background-color: inherit;
font-size: 14px;
}
hr {
height: 0.2em;
border: 0;
color: #CCCCCC;
background-color: #CCCCCC;
display: inherit;
}
p, blockquote, ul, ol, dl, li, table, pre {
margin: 15px 0;
}
a, a:visited {
color: #4183C4;
background-color: inherit;
text-decoration: none;
}
#message {
border-radius: 6px;
border: 1px solid #ccc;
display:block;
width:100%;
height:60px;
margin:6px 0px;
}
button, #ws {
font-size: 12 pt;
padding: 4px 6px;
border-radius: 5px;
border: 1px solid #bbb;
background-color: #eee;
}
code, pre, #ws, #message {
font-family: Monaco;
font-size: 10pt;
border-radius: 3px;
background-color: #F8F8F8;
color: inherit;
}
code {
border: 1px solid #EAEAEA;
margin: 0 2px;
padding: 0 5px;
}
pre {
border: 1px solid #CCCCCC;
overflow: auto;
padding: 4px 8px;
}
pre > code {
border: 0;
margin: 0;
padding: 0;
}
#ws { background-color: #f8f8f8; }
.bloop_markdown table {
border-collapse: collapse;
font-family: Helvetica, arial, freesans, clean, sans-serif;
color: rgb(51, 51, 51);
font-size: 15px; line-height: 25px;
padding: 0; }
.bloop_markdown table tr {
border-top: 1px solid #cccccc;
background-color: white;
margin: 0;
padding: 0; }
.bloop_markdown table tr:nth-child(2n) {
background-color: #f8f8f8; }
.bloop_markdown table tr th {
font-weight: bold;
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr td {
border: 1px solid #cccccc;
margin: 0;
padding: 6px 13px; }
.bloop_markdown table tr th :first-child, table tr td :first-child {
margin-top: 0; }
.bloop_markdown table tr th :last-child, table tr td :last-child {
margin-bottom: 0; }
.bloop_markdown blockquote{
border-left: 4px solid #dddddd;
padding: 0 15px;
color: #777777; }
blockquote > :first-child {
margin-top: 0; }
blockquote > :last-child {
margin-bottom: 0; }
code, pre, #ws, #message {
word-break: normal;
word-wrap: normal;
}
hr {
display: inherit;
}
.bloop_markdown :first-child {
-webkit-margin-before: 0;
}
code, pre, #ws, #message {
font-family: Menlo, Consolas, Liberation Mono, Courier, monospace;
}
.send { color:#77bb77; }
.server { color:#7799bb; }
.error { color:#AA0000; }</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="bloop_markdown"><p>There is some really deep talk going on here again. But instead of introducing even more access modifiers we probably should fix some of the existing ones. </p>
<p>Don’t get me wrong, I understand what the authors of the proposal are trying to introduce to the language, but even if such a proposal would be accepted, there will be people who would beg for <code>typepublic</code> access modifier.</p>
<p>I tried to get some attention from the community after we introduced <code>open</code> to the language, because we literally created an inconsistent area for protocols. </p>
<p>Now we have <code>open</code> vs <code>public</code> classes, where <code>open</code> means you can subclass your type from module A in module B, and <code>public</code> prevents this.</p>
<p>What’s up with protocols?</p>
<p><code>(protocol) conforming == abstract subtyping (classes)</code></p>
<p>Fixing this area would prevent the API user from using protocols which are public but not meant to be used there (at least not to be conformed to), because there was some implementation artifact that prevented the framework author from hiding such a protocol.</p>
<p>Something like “hands off from <code>_SomeName</code> protocols” could be enforced by the language rather than some convention, which some API users might not even read. </p>
<p>That said, some hacks like this should be prevented:</p>
<pre><code class="swift">struct A : _ExpressibleByBuiltinIntegerLiteral {
init(_builtinIntegerLiteral value: _MaxBuiltinIntegerType) {}
}
struct B : ExpressibleByIntegerLiteral {
init(integerLiteral value: A) {
print(type(of: value))
}
}
let b: B = 42 // prints "A"
</code></pre>
<p>We introduced an exclusive access modifier for classes which is really odd to be honest. We should extend it to protocols as well.</p>
<p>In Module A:</p>
<ul>
<li>open protocol X - can be conformed to from module B</li>
<li>public protocol Y - cannot be confronted to from module B, but instead might be used as an interface</li>
</ul>
<p></p></div><div class="bloop_original_html"><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div> <br> <div id="bloop_sign_1480674204626516992" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <br><p class="airmail_on">Am 2. Dezember 2016 um 09:56:49, Rien via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>And the funny thing is, we don’t actually _need_ access control levels.<br><br>The only purpose of access control is to enhance security/reliability by imposing restrictions on other programmers (API users).<br><br>It seems to me that in almost all discussions the arguments are mostly backwards: i.e. formulated from the perspective of the API users. Maybe because just about all programmers are API users of the OS-API? Anyway…<br><br>What I would like to see is a complete overhaul of the access control and rewrite it entirely from the perspective of the API provider.<br>I.e. give a more fine grained control to the API writer in the sense that he can specify exactly which other piece of code has access. I consider it dangerous by default to open up a scope just because another class needs occasional access. (i.e. give -for example- module access just because there is 1 other class in the module that needs that access. Inadvertently opening up access to all other classes in that module.)<br><br>An access control list could do just that. Perhaps something like:<br><br>access(type, MyFriendClass(get))<br><br>The above would provide access to the entire type (but not any children) and read-only from MyFriendClass.<br><br>A quick -off the cuff- list of access levels:<br><br>local: access only to local scope (default)<br>type: Only the type in which it is defined (no children)<br>child: The type and its children<br><type-name>: Access is granted to the type named<br>file: Access is limited to this file only<br><file-name>: Access is granted to the named file<br>module: Access is granted to the entire module<br><module-name>: Access is granted to the module with the given name<br>public: Access is granted to everybody<br><br>Further access specification could be made possible through the use of the dot-notation:<br><br><type-name>.<function-name><br><file-name>.<class-name | function-name><br><module-name>.<class-name>.<function-name><br><br>Read/write control through a parameter passing notation:<br><br><type-name>.<function-name>([[get],][set])<br><br>Examples:<br><br>access(type) var count: Int // entire type can read/write<br>access(type(get), type.incrementer) var count: Int // Entire type can read, only the incrementer function has read/write<br>access(module, FriendType, public(get)) var count: Int // Entire module can read/write, FriendType can read/write, others can only read<br><br>Regards,<br>Rien<br><br>Site: http://balancingrock.nl<br>Blog: http://swiftrien.blogspot.com<br>Github: http://github.com/Swiftrien<br>Project: http://swiftfire.nl<br><br><br><br><br>> On 01 Dec 2016, at 21:38, Brandon Knope via swift-evolution <swift-evolution@swift.org> wrote:<br>> <br>> Is anyone starting to think the current access control model will become more burdensome over time?<br>> <br>> People will want to add and subtract to it for years to come...which tells me it's not very flexible. I'm beginning to feel like it is an old style model trying to fit into a modern language. <br>> <br>> For example, fileprivate and private encourage stuffing a lot of code into one file just to use that access control level. If you want to break this into more manageable chunks you have to make it internal or move it into a new module which is very complicated to do in Xcode (I.e requiring a new target like a framework). <br>> <br>> This keeps leading me back to having submodules or creating modules on demand. I think that would open up this system to great complexity.<br>> <br>> Want to keep something private to a specific class but private to anything outside of it? Make it internal to the same "submodule". <br>> <br>> I think we could keep tacking on things to access control, but I don't think it is really solving everyone's needs. I think a more flexible system would allow people to adapt it to their needs instead of structuring everything around a rigid system that forces you to do it swift's way. <br>> <br>> On Nov 29, 2016, at 10:24 AM, Gonçalo Alvarez Peixoto via swift-evolution <swift-evolution@swift.org> wrote:<br>> <br>>> Hello, everyone!<br>>> <br>>> I would like to introduce a new proposal to swift evolution, but first I would love to run it by all of you so I get everyone's feedback and enrich it.<br>>> <br>>> This proposal consists of introducing a new typeprivate access control level which allows for members to be accessed in all extensions of a given type, whether lying within or in another file.<br>>> <br>>> You'll find the proposal draft in:<br>>> https://github.com/goncaloalvarez/swift-evolution/blob/master/proposals/NNNN-introduce-typeprivate-access-control-level.md<br>>> <br>>> Thanks in advance for taking the time to evaluate the proposal.<br>>> <br>>> Best regards,<br>>> Gonçalo<br>>> _______________________________________________<br>>> swift-evolution mailing list<br>>> swift-evolution@swift.org<br>>> https://lists.swift.org/mailman/listinfo/swift-evolution<br>> _______________________________________________<br>> swift-evolution mailing list<br>> swift-evolution@swift.org<br>> https://lists.swift.org/mailman/listinfo/swift-evolution<br><br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></div><div class="bloop_markdown"><p></p></div></body></html>