<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>I must admit that’s a very interesting approach, however to me it feels like <code>fileprivate</code> will be a really small upgrade to <code>private</code> when you actually need it. Plus you could almost do everything with <code>fileprivate</code> instead of <code>private</code>. As Carlie Monroe said it will create a new source for confusion.</p>
<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_1491245831179294976" 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 3. April 2017 um 20:35:05, Douglas Gregor 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 style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div></div><div>
<title></title>
Hello Swift Community,
<div class=""><br class=""></div>
<div class="">In rejecting <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0159-fix-private-access-levels.md" class="">SE-0159</a>, the core team described a potential direction
we would like to investigate for “private” access control that
admits a limited form of type-based access control within files.
The core team is seeking some discussion here and a motivated
volunteer to put together a proposal along these lines for review
in the Swift 4 time-frame (i.e., very soon). To be clear, the core
team it’s sure this is the right direction to go… but it appears
promising and we would *love* to be able to settle the
access-control issue.</div>
<div class=""><br class=""></div>
<div class="">The design, specifically, is that a “private” member
declared within a type “X” or an extension thereof would be
accessible from:</div>
<div class="">
<div class=""><br class=""></div>
<div class="">* An extension of “X” in the same file</div>
<div class="">* The definition of “X”, if it occurs in the same
file</div>
<div class="">* A nested type (or extension thereof) of one of the
above that occurs in the same file</div>
<div class=""><br class=""></div>
<div class="">This design has a number of apparent benefits:</div>
<div class="">+ “private” becomes the right default for “less
than whole module” visibility, and aligns well with Swift coding
style that divides a type’s definition into a number of
extensions.</div>
<div class="">+ “fileprivate” remains for existing use cases, but
now it’s use it more rare, which has several advantages:</div>
<div class="">+ It fits well with the "progressive disclosure”
philosophy behind Swift: you can use public/internal/private for a
while before encountering and having to learn about “fileprivate”
(note: we thought this was going to be true of <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0025-scoped-access-level.md" class="">SE-0025</a>, but we were clearly wrong)</div>
<div class="">+ When “fileprivate” occurs, it means there’s some
interesting coupling between different types in the same file. That
makes fileprivate a useful alert to the reader rather than,
potentially, something that we routinely use and overlook so that
we can separate implementations into extensions.</div>
<div class="">+ “private” is more closely aligned with other
programming languages that use type-based access control, which can
help programmers just coming to Swift. When they reach for
“private”, they’re likely to get something similar to what they
expect—with a little Swift twist due to Swift’s heavy use of
extensions.</div>
<div class="">+ Loosening the access restrictions on “private” is
unlikely to break existing code.</div>
<div class=""><br class=""></div>
<div class="">There are likely some drawbacks:</div>
<div class="">- Developers using patterns that depend on the
existing lexically-scoped access control of “private” may find this
new interpretation of “private” to be insufficiently strict</div>
<div class="">- Swift’s access control would go from “entirely
lexical” to “partly lexical and partly type-based”, which can be
viewed as being more complicated</div>
<div class=""><br class=""></div>
</div>
<div class="">Thoughts? Volunteer?</div>
<div class=""><br class=""></div>
<div class="">- Doug</div>
_______________________________________________<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>