[swift-evolution] access control proposal

David Owens II david at owensd.io
Tue Dec 15 11:37:25 CST 2015

> On Dec 15, 2015, at 9:17 AM, Ilya Belenkiy via swift-evolution <swift-evolution at swift.org> wrote:
> I think that I already gave simple and reasonable examples. If this was a complicated issue, I would agree that a coded example would be useful. But in this case, it looks like anything small will be called contrived, and anything big will be called poorly designed.
> I think that I already presented my case. I hope that the discussion is enough to submit a formal proposal. If not, I'll stop here.

There’s no reason to not submit a proposal for it with examples and references to the criticism in this thread and your counter for it. If nothing else, it would consolidate this thread as there have been multiple variations proposed throughout and solidify exactly what the proposal is all about.

My person vote is to not support further grain access controls. It's not because your examples were not reasonable, but because I come from a perspective where I don’t think the language complexity warrants it and the use case is very narrowly focused. Others have been in favor of it though.

So go for it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151215/5fbd6635/attachment.html>

More information about the swift-evolution mailing list