<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=""><div class="">I know that it’s been suggested a while back, but what is/was the reasoning for rejecting:</div><div class=""><br class=""></div><div class=""><ul class="MailOutline"><li class=""><b class="">public</b></li><li class=""><b class="">module</b> (same as internal in Swift 2.2)</li><li class=""><b class="">file</b> (same as private in Swift 2.2)</li><li class=""><b class="">private</b></li></ul><div class=""><br class=""></div></div><div class="">It seems pretty simple, clear, and understandable. It doesn’t make itself very useful as search terms (module or file are pretty generic), but I would assume that would be a learn-once-and-your-done thing.</div><div class="">—</div><div class="">Michael Wells</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 30, 2016, at 5:24 PM, Brent Royal-Gordon via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">I maintain that anyone with a coding convention of "always write an access modifier" will be very upset with this.<br class=""></blockquote><br class="">I doubt they'll be too pleased with `moduleprivate`, either.<br class=""><br class="">-- <br class="">Brent Royal-Gordon<br class="">Architechies<br class=""><br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></div></blockquote></div><br class=""></body></html>