<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><blockquote type="cite"><blockquote type="cite" class=""><div class=""><div class="gmail_quote"><div dir="ltr" class="">On Mon, Mar 14, 2016 at 8:18 PM Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Per Doug’s email, the core team agrees we should make a change here, but would like some bikeshedding to happen on the replacement name for private.<br class="">
<br class="">
To summarize the place we’d like to end up:<br class="">
<br class="">
- “public” -> symbol visible outside the current module.<br class="">
- “internal” -> symbol visible within the current module.<br class="">
- unknown -> symbol visible within the current file.<br class="">
- “private” -> symbol visible within the current declaration (class, extension, etc).<br></blockquote></div></div></blockquote></blockquote><br><div>I'm tempted to wade in on the KISS principle with : </div><div><br></div><div>public</div><div>internal</div><div>file</div><div>private</div><div><br></div><div>"It does what it says on the tin" :-)</div><div><br></div><div>Joanna</div><div>Carter Consulting</div><div><br></div><div>Envoyé de mon iPad</div></body></html>