<div dir="ltr"><div> * What is your evaluation of the proposal?</div><div><br></div><div><span style="font-size:12.8px;line-height:19.2px">Against.</span></div><div><span style="font-size:12.8px;line-height:19.2px"><br></span></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><br></div><div>I do not believe that this is the best way to solve the problem described.</div><div><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="font-size:12.8px;line-height:19.2px"><br></span></div><div><span style="font-size:12.8px;line-height:19.2px">I don't think, i think is the wrong direction. Visual noise is a big problem here.</span><br></div><div><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><br></div><div>In ObjC the sea of Selfs always distract me while debugging code.<br></div><div><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?</div><div><br></div><div>I read the entire thread, and i have one software we always need to use self (team accordance) and other we avoid when is possible (also team accordance) and the first team is think to remove the need because the noise.<br></div></div><br><div class="gmail_quote"><div dir="ltr">Em dom, 20 de dez de 2015 às 13:54, Kevin Lundberg via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
-1, for this reason, and for the extreme loss in conciseness already
mentioned elsewhere. The purported extra clarity is not worth the
extra burden placed on writing code in my opinion. I would favor a
compiler warning at the most, and this can be solved on an
individual/team basis with linting tools as well.</div><div bgcolor="#FFFFFF" text="#000000"><br>
<br>
<div>On 12/18/2015 1:02 AM, Jed Lewison via
swift-evolution wrote:<br>
</div>
<blockquote type="cite">
I’m not in favor of this proposal, and rather than repeat
arguments that have already been made, I thought I’d share a small
piece of data from the project I’m working on to illustrate the
impact of implicit self in terms of reducing repetitive
boilerplate cruft.
<div><br>
</div>
<div>Our project consists of a legacy ObjC code base for
an iOS app and a new version written entirely in Swift. The
feature set is largely the same in both code bases, so it’s a
good A vs B comparison.
<div><br>
</div>
<div>In the Objective C version of the app, there are
~25,000 explicit references to self. (Keep in mind that this
could easily have been a much bigger number if there weren’t
such pervasive usage of ivars in the code.).</div>
<div><br>
</div>
<div>In the Swift version, there are ~1,000 explicit
references to self, mostly in initializers and when passing
self as an argument to a protocol — and about 10% of those
would disappear with the proposal to allow implicit references
to self with a strong capture list.</div>
<div><br>
</div>
<div>I know self is just a 4-letter word, and I know
Swift’s goal isn’t to reduce character count simply for the
sake of reducing character count, but it least for our
project, avoiding “self”-blindness has really mode code more
readable.<br>
<div><br>
</div>
<div><br>
<div>
<blockquote type="cite">
<div>On Dec 16, 2015, at 1:55 PM, Douglas
Gregor via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank"><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a></a>>
wrote:</div>
<br>
<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"><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></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"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a></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"><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></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=p6o4HjCMBoFPyX01HpX5dFXtlJXHR9N02-2Ftww21omcMHRDPvlTDMzY7fVPWZi-2F-2Fxf58-2F6Q0e5WLyJ1U1A23ATr2LIxGq-2FK4SJyea0crqK3rGSWSY0jdTZDdTEmwj58F4oybGLtpkiwEq5xiZjBI3i376iH5lOhNC0qaFKeMOstRjhR6FoBZfE4cEkPreEg6YnOJtTkl0kKrI09-2FniWeJw3Em8Vdu0l9ciCVIHz5c03U-3D" alt="" 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" border="0" height="1" width="1">
</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>
</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=AxVqvhl7qaAz-2FE20TrrgNT-2F44XdgxmRgRA416dJII-2BQh709uqWh0ly4h3PuLLbhquV-2FEoTyAKbv35YA9xf8n1tYBertu7VBHtlJSOIOgkllCF-2BGouvFvl9JnubEVoW-2Fxc0nRdIOmxs-2BVV7hz6HEf8rrBy98uAkJWf1Ll-2BFfDUvTI2zCVdG-2BUkbZwhsRS8POXnHucq6GmyQA6FyOiik-2BIStJypkmemHqPY2m8tc6cJJQ-3D" alt="" 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" border="0" height="1" width="1">
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
swift-evolution mailing list
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a>
</pre>
</blockquote>
<br>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=fuWmDRE6-2FDdvdUHeLHruUfdigJaxz7nh99l6HfkulY8EENgIzOWHtiC9C7wlsx8gy6I-2B21ecymWiI4-2ButtsmNC17JQbq-2FJgZb5w5theovDCCADq2Q5AJSXUbrApvrX4Zyle4wlPMpWPrGH8MtSq50bbJNUZMP4Vhrrp9fpZQ76FeXHOWV6YzB2GE8SaA8TPg1kxRh8ECeOCF-2BvEr-2FHAdiFueoI84DWKhUAKn9SxVm7w-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>
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>
</blockquote></div>