[swift-evolution] [swift-evolution-announce] [Review #3] SE-0117: Allow distinguishing between public access and public overridability
shawnce at gmail.com
Thu Jul 21 11:54:14 CDT 2016
(Google inbox won't let me inline my comments)
Thanks for the effort on iterating and refining this proposal.
+1 on the proposal, more strongly favoring the first design.
If my brain is working correctly it seems like we could start with the
first design and if somehow problematic move to the the second model in the
future without (much?) disruption. I didn't sit down and reason it out in
much depth (watching my 2.5 year old at the moment) however so I will leave
that to others to ponder.
I think it aligns well with Swifts principles in terms of favoring external
to module API to be intentional / explicit. The latest revisions - I think
- has also sufficiently reduced the burden to module developers which is
also another important aspect of Swift.
I haven't used a language the has this exact type of feature but I have
often desired to haven his type of capability when I was authoring
libraries for others (often in company). I am a believer in being very
explicit in API contract to both confine what I have to design for/test
when authoring a library as well as having more clarity when consuming a
On Thu, Jul 21, 2016 at 11:33 AM Chris Lattner <clattner at apple.com> wrote:
> Hello Swift community,
> The third review of "SE-0117: Allow distinguishing between public access
> and public overridability" begins now and runs through July 25. The
> proposal is available here:
> Reviews are an important part of the Swift evolution process. All reviews
> should be sent to the swift-evolution mailing list at
> or, if you would like to keep your feedback private, directly to the
> review manager.
> What goes into a review?
> The goal of the review process is to improve the proposal under review
> through constructive criticism and contribute to the direction of Swift.
> When writing your review, here are some questions you might want to answer
> in your review:
> * What is your evaluation of the proposal?
> * Is the problem being addressed significant enough to warrant a
> change to Swift?
> * Does this proposal fit well with the feel and direction of Swift?
> * If you have used other languages or libraries with a similar
> feature, how do you feel that this proposal compares to those?
> * How much effort did you put into your review? A glance, a quick
> reading, or an in-depth study?
> More information about the Swift evolution process is available at
> Thank you,
> -Chris Lattner
> Review Manager
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution