<div dir="ltr"><div><span style="font-size:13px">* What is your evaluation of the proposal?</span><br></div> -1. I vote against this proposal. I believe that a linter and/or an in house code guide is the best place to manage this.<div><br></div><div><div style="font-size:13px">* Is the problem being addressed significant enough to warrant a change to Swift?<br></div><div style="font-size:13px"> I think that it is a significant concern but, as I stated above, best handled with tooling.</div><div style="font-size:13px">* Does this proposal fit well with the feel and direction of Swift?<br></div><div style="font-size:13px"> No. The current Swift behavior around this issue is clear and is reasonable to many.</div><div style="font-size:13px">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</div></div><div style="font-size:13px"> I have followed the thread and have had this discussion many times.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 16, 2015 at 5:47 PM, T.J. Usiyan <span dir="ltr"><<a href="mailto:griotspeak@gmail.com" target="_blank">griotspeak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Creating that summary seems like it would be a large burden to place on whoever manages the review. I don't think that that is worth the effort when the responses *are* readily available.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 16, 2015 at 3:09 PM, Nick Shelley via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:12.8px">All of the prior swift-evolution commentary on this proposal (which is nearing the 100-message mark) will also be considered, of course!</span></blockquote><div><br></div></span><div>It is my opinion that the proposal should encapsulate as much of that discussion as possible so every reviewer doesn't have to read every comment in that thread. The current proposal is wildly one-sided and seems to only reflect the opinion of its author and those who agree with the proposal. I created a Pull Request (<a href="https://github.com/apple/swift-evolution/pull/59" target="_blank">https://github.com/apple/swift-evolution/pull/59</a>, still not merged and no comments as to why) to more fairly represent the single counter-argument pointed out in the proposal, but others in the mailing list expressed concern that none of the other downsides of the proposal are represented at all.</div><div><br></div><div>Is my (and others') desire to have the proposal contain an accurate representation of the main points of the community discussion off base? Is the main purpose of the proposal to be a sales pitch for an idea, even if it includes building up and tearing down straw-man versions of the arguments brought forth by the opposition? I'm asking with sincere curiosity because I can't seem to find a good description of the purpose of the proposal in my research of how the evolution process works.</div><div><br></div><div>Thanks in advance for clarifying these points for me.</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 16, 2015 at 11:58 AM, Douglas Gregor via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">All of the prior swift-evolution commentary on this proposal (which is nearing the 100-message mark) will also be considered, of course!<div><br></div><div><span style="white-space:pre-wrap"> </span>- Doug<br><div><br><div><blockquote type="cite"><div><div><div>On Dec 16, 2015, at 10:55 AM, Douglas Gregor via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br></div></div><div><div><div><div style="word-wrap:break-word">Hello Swift community,<div><br><div>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><br></div><div><span style="white-space:pre-wrap"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0009-require-self-for-accessing-instance-members.md</a></div><div><br></div><div><div>Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at</div><div><br></div><div><span style="white-space:pre-wrap"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></div><div><br></div><div>or, if you would like to keep your feedback private, directly to the review manager.</div><div><br></div><div>What goes into a review?</div><div><br>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><br><div><span style="white-space:pre-wrap"> </span>* What is your evaluation of the proposal?<br></div><div><span style="white-space:pre-wrap"> </span>* Is the problem being addressed significant enough to warrant a change to Swift?<br></div><div><span style="white-space:pre-wrap"> </span>* Does this proposal fit well with the feel and direction of Swift?<br></div><div><span style="white-space:pre-wrap"> </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></div><div><span style="white-space:pre-wrap"> </span>* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br></div><br></div><div>More information about the Swift evolution process is available at</div><div><br></div><div><span style="white-space:pre-wrap"> </span><a href="https://github.com/apple/swift-evolution/blob/master/process.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a></div><div><br></div><div><span style="white-space:pre-wrap"> </span>Cheers,</div><div><span style="white-space:pre-wrap"> </span>Doug Gregor</div><div><span style="white-space:pre-wrap"> </span>Review Manager</div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=XbU4wxnU83GyR7TGhOdBtBOchMF7PYvaYPXWDKda2ffqX-2BT18BxAwYLO-2BpcXBRy5XplLrZqRUgm2BTqTYbF-2FCRM0sp6as2nRXCfOll-2BwWZl1e3uzq-2FA7SZ2AlxwHWsBP82ja8YjdgkPtsOLlkWfXRCkIvATzzCE6vfTL2j8n0ywCQu7leMBb3iCJJNCl6vqlM-2BLvplDbi2Z-2BA6jxEdbrj-2B0KHLY0d-2FINL-2BM-2B2BpszbM-3D" alt="" width="1" height="1" border="0" style="min-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">
</div></div></div>
_______________________________________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=Kyo40-2Fb6mK7qqe0u18o4nlmNW45gwtJGUNOsveb6UxNlmQ70vEobGW8cEvZqY4Lr0hxEVzgHCh7jrzLXV1TDuTefWYny7UXOvubmKqtrqkLnbU7qkN3Z1HNrbt9-2FKOs5nrnH6xfJOl1qXjrrKtQije6iGtU5jHkBezuHiVkY1Vevk3o0Dgm6T-2BZsl1y4RYz1dGhxKlSsLS-2BUI2JkmEjILSpidQueD918LGH8aF9ZtRk-3D" alt="" width="1" height="1" border="0" style="min-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">
</div>
<br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=3FGfocPbgxkNkmje7djckg9Iw-2BGYY3X6RxJ1tkUXKCo0WkFbz1emDhZkKCoIUzd4r-2BDIrNvWRjLucFEHy6KsOrnTZ341AkKRblgGoo-2FIyh9Oxc0cmaTeXn4iYHPFiWaHFDwSsSsgNjtRPwOkB6TQskSXoEuQVwDTbjmvpZkvb5qW2gVaboVi9t81-2F-2Bk-2FnZAD-2BnqU-2BGe4gN0e8SqQ5wJdZuoYQ-2BqgSbBo2quRqNwej7o-3D" alt="" width="1" height="1" border="0" style="min-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">
</div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>