<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="" style="font-family: HelveticaNeue;">* What is your evaluation of the proposal?</b><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;">Against.</div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;"><div class="">As self.an self.example, self.you can self.see how much self.harder it is to self.understand this self.sentence. We self.are self.not self.designed to self.scan words with self.self. in self.front of self.them.</div><div class=""><br class=""></div></div><div class="" style="font-family: HelveticaNeue;">The problem with this proposal is simply that using “self.blah” all over the place makes the code less readable. Yes, it can eliminate a certain class of programmer errors. But, for example, I could argue that we could eliminate a certain class of programmer errors if every time we typed in a variable we had to manually enter its type, so like,</div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;">foo = foo + 1</div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;">must be</div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;">foo.Int = foo.Int + 1.Int</div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;">Obviously this is a pathological example because the compiler would catch the error in this case anyhow, but my point is that extra words have a cost in terms of programmer comprehension, and sometimes the cost isn’t worth an incremental gain in safety.</div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;">Right now Swift is extremely readable and clean. Let’s keep it that way!</div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;"><br class=""></div><div class="" style="font-family: HelveticaNeue;"><div class=""><div class="" style="font-family: Helvetica;"><div class=""><b class="">* Is the problem being addressed significant enough to warrant a change to Swift?</b><br class=""></div><div class=""><br class=""></div><div class="">The problem is big enough but the solution isn’t good enough.</div><div class=""><br class=""></div><div class=""><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=""><br class=""></div><div class="">It would if I agreed with the solution.</div><div class=""><br class=""></div><div class=""><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=""><br class=""></div><div class="">I’ve used Objective-C for 26 years, although obviously the “self.” style properties are (relatively) recent.</div><div class=""><br class=""></div><div class=""><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’ve coded a ton in Swift and considered the arguments for. I also briefly considered this proposal myself a while ago, but decided that it was just too wordy to be worth the extra safety.</div><div class=""><br class=""></div></body></html>