<div dir="ltr"><div class="markdown-here-wrapper" style=""><p style="margin:0px 0px 1.2em!important">No idea if this will be useful, or if it will work, but I created a public trello board:</p>
<p style="margin:0px 0px 1.2em!important"><a href="https://trello.com/b/fmv4uV3n/swift-access-control">https://trello.com/b/fmv4uV3n/swift-access-control</a></p>
<ul style="margin:1.2em 0px;padding-left:2em">
<li style="margin:0.5em 0px">Pre-populated with a few of the things already mentioned.</li>
<li style="margin:0.5em 0px">There’s a link on the board to gain edit access.</li>
</ul>
<p style="margin:0px 0px 1.2em!important">It’s possible this will be an utter disaster, or that nobody will use it at all, so go ahead and add new lists/cards with abandon.</p>
<div title="MDH:PGRpdj5ObyBpZGVhIGlmIHRoaXMgd2lsbCBiZSB1c2VmdWwsIG9yIGlmIGl0IHdpbGwgd29yaywg
YnV0IEkgY3JlYXRlZCBhIHB1YmxpYyB0cmVsbG8gYm9hcmQ6PGJyPjxicj48YSBocmVmPSJodHRw
czovL3RyZWxsby5jb20vYi9mbXY0dVYzbi9zd2lmdC1hY2Nlc3MtY29udHJvbCI+aHR0cHM6Ly90
cmVsbG8uY29tL2IvZm12NHVWM24vc3dpZnQtYWNjZXNzLWNvbnRyb2w8L2E+PGJyPjxicj48L2Rp
dj48ZGl2PiogUHJlLXBvcHVsYXRlZCB3aXRoIGEgZmV3IG9mIHRoZSB0aGluZ3MgYWxyZWFkeSBt
ZW50aW9uZWQuPGJyPiogVGhlcmUncyBhIGxpbmsgb24gdGhlIGJvYXJkIHRvIGdhaW4gZWRpdCBh
Y2Nlc3MuPGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+SXQncyBwb3NzaWJsZSB0aGlzIHdp
bGwgYmUgYW4gdXR0ZXIgZGlzYXN0ZXIsIG9yIHRoYXQgbm9ib2R5IHdpbGwgdXNlIGl0IGF0IGFs
bCwgc28gZ28gYWhlYWQgYW5kIGFkZCBuZXcgbGlzdHMvY2FyZHMgd2l0aCBhYmFuZG9uLjxicj48
YnI+PC9kaXY+" style="height:0;width:0;max-height:0;max-width:0;overflow:hidden;font-size:0em;padding:0;margin:0"></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, 2 Dec 2016 at 22:38 Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well, that's literally what I just mentioned above. I'd be fine with getting rid of private and fileprivate.<br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Fri, Dec 2, 2016 at 16:30 Jonathan Hull <<a href="mailto:jhull@gbis.com" class="gmail_msg" target="_blank">jhull@gbis.com</a>> wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Dec 2, 2016, at 2:21 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="gmail_msg" target="_blank">xiaodi.wu@gmail.com</a>> wrote:</div><br class="m_1084301622453376980m_-6858905872626469706Apple-interchange-newline gmail_msg"><div class="gmail_msg">I'm not sure why that last scenario couldn't be accommodated by submodules. Why wouldn't you put those two specific submodules in the same parent submodule?<br class="gmail_msg"></div></blockquote><div class="gmail_msg"><br class="gmail_msg"></div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">Why even have private and fileprivate? Why not just make everything internal? Same reason…</div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div><br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Fri, Dec 2, 2016 at 15:35 Jonathan Hull 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"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">Assuming that this is true (I tend to agree), why do we need any extra syntax at all? Couldn’t we just make everything accessible to extensions?<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Alternatively, if we do want to hide some things from extensions by default (to prevent accidental use), I had a proposal a while back which had a very simple way to control what is shared. Basically, you could have a special import statement which allows you to extend knowledge/access of the hidden parts to another file (you were also able to limit the range of this ability if needed).</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">Most of the feedback at the time seemed to want submodules instead, but I still think there will still eventually be a need for something like this. As others have mentioned, the current system is inflexible (especially to the common use cases), causing people to keep requesting additions… and forcing them to give wider access than they want to in the mean time. Even if we have sub-modules, someone will want to share with a specific other sub-module, but not make things public.</div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Dec 1, 2016, at 1:31 AM, Tino Heth via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br class="gmail_msg m_1084301622453376980m_-6858905872626469706m_-3605580025006761637Apple-interchange-newline"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="gmail_msg">It also means that anybody who want to access your private var will just have to write an extension to expose it.</div></div></blockquote></div>imho this is wrong thinking:<div class="gmail_msg">Access control is no tool to offer real "protection" — it can't stop someone who wants to break a system.</div><div class="gmail_msg">Especially in the world of open source, it is merely an advice from the author not to do certain things.</div></div>_______________________________________________<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" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg"></div></blockquote></div><br class="gmail_msg"></div></div></div>_______________________________________________<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">
</blockquote></div>
</div></blockquote></div></div></blockquote></div>
_______________________________________________<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">
</blockquote></div>