<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="">Sorry if I wasn’t expressing myself well enough. In my original email, I said that:</div><div class=""><br class=""></div><div class="">> The new rules make `private` more prominent compared to `fileprivate` (the latter has a somewhat worse name).</div><div class=""><br class=""></div><div class="">So I agree that my issue is more with the naming than the functionality. I’m mainly complaining that because of its name, `fileprivate` feels like more of a special corner case of `private`. But in the style of writing types through extensions, `fileprivate` will become much more prevalent than `private`, which feels slightly backwards.</div><div class=""><br class=""></div><div class="">But I don’t want to dabble too much about it. If its the way it’s going to be, so be it.</div><br class=""><div><blockquote type="cite" class=""><div class="">On 29 Jun 2016, at 15:11, Matthew Johnson <<a href="mailto:matthew@anandabits.com" class="">matthew@anandabits.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">There is nothing preventing you from using fileprivate if you want to write your code in this style. At most you can complain that you don't like the new keyword. But you're not losing any functionality so I don't understand why you say you are "missing" something.</div><div class=""><br class="">Sent from my iPad</div><div class=""><br class="">On Jun 29, 2016, at 1:25 AM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 29 Jun 2016, at 04:03, Matthew Judge <<a href="mailto:matthew.judge@gmail.com" class="">matthew.judge@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 14px; 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; float: none; display: inline !important;" class="">If I understand SE-0025 (even with the amendment) you can still spell the access modifier to types as 'private' and get the same characteristics as the pre-SE-0025 meaning or private, so I'm not sure I understand the concern here. However (continued below)</span></div></blockquote></div><br class=""><div class="">The characteristic I will be missing is for the following style of writing:</div><div class=""><br class=""></div><div class="">class MyViewController : UIViewController {<br class=""> private var privateInfo: String?<br class="">}<br class=""><br class="">//MARK: Public<br class=""><br class="">public extension MyViewController {<br class=""> func publicFunction() {<br class=""> // CAN’T ACCESS privateInfo<br class=""> }<br class="">}<br class=""><br class="">//MARK: UITableViewDataSource<br class=""><br class="">private extension MyViewController : UITableViewDataSource {<br class=""> func numberOfRowsInSection(_ section: Int) -> Int<br class=""> // CAN’T ACCESS privateInfo<br class=""> }<br class="">}<br class=""><br class="">//MARK: Private<br class=""><br class="">private extension MyViewController {<br class=""> func implementationFunction() {<br class=""> // CAN’T ACCESS privateInfo<br class=""> }<br class="">}</div></div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></blockquote></div></div></blockquote></div><br class=""></body></html>