<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-1 (in it’s current form)</div><div class=""><br class=""></div><div class="">I’m concerned about decreasing the signal/noise ratio.</div><div class="">The current way is similar to type inference. We can’t immediately see the type, but tool support makes it easy to retrieve the information if needed. And most of the time, i.e. when just scanning the code, there is simply less information to work through.</div><div class="">With less syntax, the code structure becomes clearer than when every second word is “self”.</div><div class="">As such, I don’t think the proposal in its current form fits well with Swift, which is very good at keeping code “to the point”.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="">I wonder if leaving out “self”, but keeping the dot would be a better alternative. There is precedent in Swift (c.f. enums), the dot is easier to ignore when skimming the code and it’s still immediately obvious when you want to know.</div><div class="">Ruby does something similar (using @) and it feels muss less heavy than “self.” in Objective-C while having most of the benefits. Any other single character would work, too, of course.</div><div class=""><br class=""></div><div class="">Example:</div><div class=""><br class=""></div><div class="">class Person {<div class=""> var name: String = "David"</div><div class=""> func foo() {</div><div class=""> print("Hello \(.name)")</div><div class=""> }</div><div class=""> </div> func bar() {<div class=""> .foo()</div><div class=""> }</div><div class="">}</div></div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="">I think the problem is significant enough that it might warrant *a* change to Swift, but not the proposed one. The costs are higher than the benefits compared to my current solution (which is very clear syntax highlighting).</div><div class="">I do question if the problem occurs frequently enough (or at all) when it comes to methods.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Nik</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 16 Dec 2015, at 19:55, Douglas Gregor <<a href="mailto:dgregor@apple.com" class="">dgregor@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello Swift community,<div class=""><br class=""><div class="">The review of “Require self for accessing instance members” begins now and runs through Sunday, December 20th. The proposal is available here:</div></div><div class=""><br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.md</a></div><div class=""><br class=""></div><div class=""><div class="">Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at</div><div class=""><br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div><div class=""><br class=""></div><div class="">or, if you would like to keep your feedback private, directly to the review manager.</div><div class=""><br class=""></div><div class="">What goes into a review?</div><div class=""><br class="">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:<br class=""><br class=""><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>* What is your evaluation of the proposal?<br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>* Is the problem being addressed significant enough to warrant a change to Swift?<br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>* Does this proposal fit well with the feel and direction of Swift?<br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br class=""></div><br class=""></div><div class="">More information about the Swift evolution process is available at</div><div class=""><br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span><a href="https://github.com/apple/swift-evolution/blob/master/process.md" class="">https://github.com/apple/swift-evolution/blob/master/process.md</a></div><div class=""><br class=""></div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>Cheers,</div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>Doug Gregor</div><div class=""><span style="white-space: pre;" class="Apple-tab-span"> </span>Review Manager</div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=LyN2ZYORolPMXQaaZ3N0rxUhjJXYzDOcDPswkVWZ4gYq5dM7MWvOA-2Fer-2B4SthBPMPDA-2FSaxEKaEjFiSgrUkaDaRD58GWKo-2B1pBqwKXEtOQGxscvpnqsEdgqZlglMn1YO20nBV1yXcb4kmZwXQgHIZC4Fbw7uEV8qA3tqYUIOfwt8qSNRtCAnm3pzocRYEvIedjC9QKJV17rr7wS0WpNO3g-3D-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-evolution-announce mailing list<br class=""><a href="mailto:swift-evolution-announce@swift.org" class="">swift-evolution-announce@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution-announce<br class=""></div></blockquote></div><br class=""></body></html>