<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 28, 2016, at 14:23, David Waite <<a href="mailto:david@alkaline-solutions.com" class="">david@alkaline-solutions.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Mar 28, 2016, at 2:30 PM, Jordan Rose via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">P.S. Extensions do make things a little more complicated, but again, there's almost no precedent here, and pretty much everyone agrees that this new scope-private access level shouldn't give access to extensions. That also means there's an option to keep yourself from accidentally accessing scope-private members in a member type: put the member type in an extension.</div></div></blockquote><div class=""><br class=""></div>The only example that comes to mind is Ruby, where I can add new methods to an existing class, and those new methods indeed have access to existing ‘private’ methods:</div><div class=""><br class=""></div><div class="">class A</div><div class=""> private def foo()</div><div class=""> puts “foo called”</div><div class=""> end</div><div class="">end</div><div class=""><br class=""></div><div class="">A.new.foo() # error</div><div class=""><br class=""></div><div class="">class A</div><div class=""> def bar() # add new bar method</div><div class=""> foo()</div><div class=""> end</div><div class="">end</div><div class=""><br class=""></div><div class="">A.new.bar() # prints “foo called”</div></div></div></blockquote><br class=""></div><div>Yeah, I tried to sweep that under the rug by noting that Ruby's definition of "private" didn't match up with either Java-private or current-Swift-private anyway, but it's true that someone coming from Ruby might expect this to work.</div><div><br class=""></div><div>Jordan</div><br class=""></body></html>