<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="">I've been following the thread for some days and being the community quite separated in this makes it a hard decision. </div><div class=""><br class=""></div><div class="">Honestly I've been using self. in my Swift code most of the time, for me it makes things more explicit and removes any confusion that can happen. That said, I say "most of the time" because is really true that it feels nicer to not include it. </div><div class=""><br class=""></div><div class="">I would like to point out that being explicit is not necessary a bad thing, as Swift already force us to being explicit in some ways (optionals, throws, etc) as the proposal says, but specially that, IMHO, we should not decide if things that affect directly the code that we write and, specially, read should be omitted because another tool makes it obvious. In other words, that an IDE colorizes the text is not enough to discard it. We read a lot of code from the internet, specially PR, and we can not rely on having always an IDE to make things explicit.</div><div class=""><br class=""></div><div class="">That said, seeing that the community is so separated in this and that the language doesn't enforce it already (which looks like the core team didn't think that it that important for being part of the core language) I would say that having this enforced by a linter or a compiler warning (that can be disabled) may be enough. </div><div class=""><br class=""></div><div class="">Sorry for not having a stronger opinion, but I wanted to add my opinion to the review ;)</div><div class=""><br class=""></div><div class="">PS: I agree that maybe the proposals should contain more of the opinions in the mailing list, at least in cases like this that have been so many mails and not everyone can keep up with it. Cheers.</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">El 16 dic 2015, a las 18:55, Douglas Gregor via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> escribió:</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 class="Apple-tab-span" style="white-space: pre;"> </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 class="Apple-tab-span" style="white-space: pre;"> </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 class="Apple-tab-span" style="white-space: pre;"> </span>* What is your evaluation of the proposal?<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>* Is the problem being addressed significant enough to warrant a change to Swift?<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>* Does this proposal fit well with the feel and direction of Swift?<br class=""></div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </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 class="Apple-tab-span" style="white-space: pre;"> </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 class="Apple-tab-span" style="white-space: pre;"> </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 class="Apple-tab-span" style="white-space: pre;"> </span>Cheers,</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Doug Gregor</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Review Manager</div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=ugfoipfLFYQJoLOuZfhEMRzWwNIL3Gkut5GUvNxqU0ebNQTGr9XK-2FON4C-2FtWKT8pd7R6kJCd2IylgKi1JnLxvFf4bN1JFhrIO-2BoJRYv96uv5YzMG-2B2oRlCC3201gT5mLhUzy8tTF8FVPwPDHqZ-2FtYka7G6yfHgBtt53yTcTW5fccMFW4i-2FdvQVp53Wddk0-2FGcfibV0GL7UXQ5Mx7BltmrbeuZTqOQ4m9hUcQz5gLWQM-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 mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>