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

[Paul Ossenbruggen]

Hello Swift Evolution! What a wonderful discussion going on here :)

== What is your evaluation of the proposal? ==
== Does this proposal fit well with the feel and direction of Swift? ==

I don’t want to be forced use self everywhere, i think if your team wants to enforce it then a linter can solve this issue. I am against adding clutter. When things are clear. 

== Is the problem being addressed significant enough to warrant a change to Swift? ==

No I don’t think so. 

== If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those? ==

I could deal with some syntax that made it clear you were using an instance. For instance prefixing with a dot but that could conflict with enums. It would have to be very minimal though. 

== How much effort did you put into your review? ==

the time to read proposal and read email discussions. 
>> 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> <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> <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
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151216/66b50e7c/attachment.html <https://lists.swift.org/pipermail/swift-evolution/attachments/20151216/66b50e7c/attachment.html>>
> 
> 
> _______________________________________________
> 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/bd400074/attachment.html>