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

[Jacopo Andrea Giola]

 * What is your evaluation of the proposal?
	-1 I don’t support this proposal
	
    * Is the problem being addressed significant enough to warrant a change to Swift?
	For me not really, even if I can’t agree with people that sustain the thesis which syntax highlighting is a sufficient way to recognise local variable against instance properties.
	
    * Does this proposal fit well with the feel and direction of Swift?
	Swift value brevity and clarity and accepting this proposal will add a lot of noise, not counting the fact that in Swift 3 will likely break almost all the swift code available in the short term (and I don’t think that an automation translation can do always the right thing).
	
    * If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
	I’ve only used Obj-C extensively but in terms of values is like the opposite of Swift about brevity.
	For me the implicit self was one of the best features announced with Swift.  

    * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
	I’ve followed sparingly the discussion and I’ve read the official proposal on GitHub and all the response on this thread.

- Jacopo

> On Wed, Dec 16, 2015 at 1:55 PM, Douglas Gregor via swift-evolution <swift-evolution at swift.org <mailto: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 <mailto:swift-evolution at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151217/e14521cb/attachment.html>