<div>I agree it would be hard. In fact, it would be the most difficult part about it. Like how the API team at Apple will debate for weeks the name of a foundation method. </div><div><br></div><div>Another counter point to my theory is that most developers will go for the automatic "private var". So there would definitely be a habitual ritual learning curve. But imagine how much more accurate and descriptive it would be for new folks. And Crustys (like me) can claim a terse semantic victory, although having to relearn some mental autopilot routines.</div><div><br></div><div><br><div class="gmail_quote"><div>On Fri, Mar 24, 2017 at 9:42 AM Sean Heber <<a href="mailto:sean@fifthace.com">sean@fifthace.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This line of thought seems worth some consideration - why require a mental mapping from the meaning of “public” to what it *really* is when it could just say what it means? Although I admit that coming up with decent words or nice phrasings might be harder than it seems. :)<br class="gmail_msg">
<br class="gmail_msg">
l8r<br class="gmail_msg">
Sean<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
> On Mar 24, 2017, at 6:12 AM, Vinnie Hesener 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">
><br class="gmail_msg">
> I like the idea of changing some reserved words. Aren't 'private', 'friend, 'public', 'internal', etc just metaphors that were built on top of object encapsulation (another metaphor)? I think we're starting to see the limits of stretching metaphoric syntax.<br class="gmail_msg">
><br class="gmail_msg">
> Why can't we just start naming access modifiers literally: a location in the code that they apply to. Examples such as "scope" or "insidethecurlybraces" or "file" or "module" or "submodule" or "codebase". Any of these or other synonyms would be much more Swifty in my opinion.<br class="gmail_msg">
> _______________________________________________<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">
<br class="gmail_msg">
</blockquote></div></div>