<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><font color="#000000"><span style="background-color: rgba(255, 255, 255, 0);">Presumably, proponents of SE-0025. That is, after all, an explicit part of that design, reviewed and approved by the Swift community and core team.</span></font></div></div></div></blockquote><br></div><div>I'd be curious how many people actually are doing this though. My understanding is this practice is not that common overall.</div><div><br></div><div>Ultimately though, yes with any change like this there will be compromises. I personally believe the loss of this situation you're describing is far less than what there is to gain from this proposal.</div><div><br></div><div>On Apr 6, 2017, at 5:48 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com">xiaodi.wu@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">On Thu, Apr 6, 2017 at 7:38 PM, Charles Srstka <span dir="ltr"><<a href="mailto:cocoadev@charlessoft.com" target="_blank">cocoadev@charlessoft.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span><blockquote type="cite">On Apr 6, 2017, at 7:34 PM, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br></blockquote><div><blockquote type="cite"><br class="m_86460104315027634m_1085067803240797926Apple-interchange-newline"><div><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">`private` works for extensions exactly how the authors of SE-0025 intended it to do. Your comments do not address what would happen for those people who are making use of this functionality currently to isolate methods to the extension only.</span></div></blockquote></div><br></span><div>Who is currently doing that?</div></div></blockquote><div><br></div><div>Presumably, proponents of SE-0025. That is, after all, an explicit part of that design, reviewed and approved by the Swift community and core team.</div></div></div></div>
</div></blockquote></body></html>