[swift-evolution] [Accepted with Revision] SE-0177: Allow distinguishing between public access and public overridability
Nevin Brackett-Rozinsky
nevin.brackettrozinsky at gmail.com
Wed Jul 27 20:06:41 CDT 2016
>
> The third review of "SE-0177: Allow distinguishing between public access
> and public overridability" ran from Active review July 21...25. The
> proposal has been *accepted with revisions*.
The third review of "SE-0177: Allow distinguishing between public access
> and public overridability"
The third review of "SE-0177
SE-0177
…did someone already buy the core team a barrel of whiskey and I missed the
chance to chip in?
:-P
I second everything Scott said: The final result looks great—excellent job
everyone, especially the core team!
Nevin
>
On Wed, Jul 27, 2016 at 6:06 PM, Chris Lattner via swift-evolution <
swift-evolution at swift.org> wrote:
> Proposal Link:
> https://github.com/apple/swift-evolution/blob/master/proposals/0117-non-public-subclassable-by-default.md
>
> The third review of "SE-0177: Allow distinguishing between public access
> and public overridability" ran from Active review July 21...25. The
> proposal has been *accepted with revisions*.
>
> This proposal was far better received by the community than previous
> versions of the proposal, and the “first design” was the favored path
> within it. However, there were some concerns raised about the complexity
> of the model, stemming from non-obvious combinations like “open private”.
> As such, the core team has requested that the proposal be revised to make
> “open” function as another access control specifier. “open” is now simply
> “more public than public”, providing a very simple and clean model.
>
> John has already revised the proposal to the new model, I encourage you to
> read it if you haven’t already.
>
> Thank you to John McCall and also Javier Soto for driving this discussion
> forward! John is already working on an implementation of this now.
>
> -Chris Lattner
> Review Manager
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160727/81b7ca71/attachment.html>
More information about the swift-evolution
mailing list