I'm disappointed in this turn of events. While I thought that accepting SE-0159 would have been a better outcome than rejecting it, I am certain that this is an inferior choice to both of those outcomes.<br><br>The key problem isn't principally _what_ this proposed private is. It is that, if adopted, this would be the third flavor of private in as many years. It is a new design with its own kinks (what to do about `private extension`, for example?) and the resultant churn would be most unfortunate.<br><div class="gmail_quote"><div dir="ltr">On Mon, Apr 3, 2017 at 14:50 David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">The problem I see with that is that it would introduce orthogonal access levels whereas they have all been hierarchal in nature up to now.</div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On 3 Apr 2017, at 21:36, Charles Srstka <<a href="mailto:cocoadev@charlessoft.com" class="gmail_msg" target="_blank">cocoadev@charlessoft.com</a>> wrote:</div><br class="m_-8155954560700050273Apple-interchange-newline gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><blockquote type="cite" class="gmail_msg">On Apr 3, 2017, at 2:28 PM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:<br class="gmail_msg"></blockquote><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><br class="m_-8155954560700050273Apple-interchange-newline gmail_msg"><div class="gmail_msg"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="gmail_msg">Btw, I know what I'm going to propose is a bit crazy, but how about making private visible to extensions even outside the file but in the same module?</span></div></blockquote></div><br class="gmail_msg"><div class="gmail_msg">That’s actually what I suggested in my original post on the topic. My feeling was that it would allow breaking a particularly large type into separate files, thus alleviating the “huge file” problem that Swift has (and which Charlie Monroe brought up as a concern).</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">It’s still what I’d prefer personally, although I can understand why the core team might want to restrict it to files.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Charles</div><div class="gmail_msg"><br class="gmail_msg"></div></div></div></blockquote></div><br class="gmail_msg"></div></div>_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>