[swift-evolution] [Review] Require self for accessing instance members

Erica Sadun erica at ericasadun.com
Wed Dec 16 14:18:32 CST 2015

I vote against this proposal. 

I believe instance-member access outside of closures is better addressed with in-house standards rather than language-mandated supervision. Swift's clarity and readability are its strengths and this proposal works against those design goals. I endorse using self when it makes sense to do so but I don’t like the idea of a heavy-handed universal language-mandate. If effort equates to "venting loudly and often about the inadvisable nature of this proposal", I have put significant effort into reviewing this proposal.

I hold my vote to be `self`-evident that not all language enhancements are created equal, and that we are endowed by our compiler with certain unalienable rights, that among these are simplicity, elegance, and the pursuit of our own coding standards.

-- Erica

> On Dec 16, 2015, at 11:55 AM, Douglas Gregor via swift-evolution <swift-evolution at swift.org> wrote:
> Hello Swift community,
> The review of “Require self for accessing instance members” begins now and runs through Sunday, December 20th. The proposal is available here:
> 	https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.md <https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.md>
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> 	https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 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, eventually, determine 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 you 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
> 	https://github.com/apple/swift-evolution/blob/master/process.md <https://github.com/apple/swift-evolution/blob/master/process.md>
> 	Cheers,
> 	Doug Gregor
> 	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/20151216/794c26e1/attachment.html>

More information about the swift-evolution mailing list