<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=""><b class="">* What is your evaluation of the proposal?</b><div class=""><br class=""></div><div class="">I’m strongly against it.</div><div class=""><br class=""><div><div class="" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div class=""><b class="">* Is the problem being addressed significant enough to warrant a change to Swift?</b><br class=""></div><div class="" style="font-weight: normal;"><br class=""></div><div class="" style="font-weight: normal;">I don’t think so.</div><div class="" style="font-weight: normal;"><br class=""></div><div class="" style="font-weight: normal;">I, personally, never encountered a bug due to this problem, and it would be really easy to fix.</div><div class="" style="font-weight: normal;"><br class=""></div><div class="" style="font-weight: normal;">I hear that such bugs might be difficult to track, and there might be ways to help to detect them, but I’m not convinced by the proposed solution.</div><div class="" style="font-weight: normal;"><br class=""></div><div class="">It seems more like a matter of taste, and the proposed solution would remove choice.</div><div class="" style="font-weight: normal;"><br class=""></div><div class=""><b class="">* Does this proposal fit well with the feel and direction of Swift?</b><br class=""></div><div class="" style="font-weight: normal;"><br class=""></div><div class="" style="font-weight: normal;">I don’t think so.</div><div class="" style="font-weight: normal;"><br class=""></div><div class="" style="font-weight: normal;">I think Swift should be concise when that doesn’t hinder clarity. (And in this case, I’m afraid it is explicitness that would hinder clarity).</div><div class="" style="font-weight: normal;"><br class=""></div><div class="" style="font-weight: normal;">Also, it seems to me implicit self makes properties and methods first-class citizens, and I think they should be.</div><div class="" style="font-weight: normal;"><br class=""></div><div class=""><b class="">* If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</b><br class=""></div><div class="" style="font-weight: normal;"><br class=""></div><div class="" style="font-weight: normal;">Yes: Objective-C, and I was glad, migrating to Swift, to get rid of all those explicit self.</div><div class="" style="font-weight: normal;"><br class=""></div><div class=""><b class="">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</b><br class=""></div><br class=""></div></div>I followed most of the thread.</div></body></html>