<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="">Hey Patrick,<div class=""><br class=""></div><div class="">Thanks for the feedback. A couple comments below:</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 12, 2016, at 2:16 PM, Patrick Gili via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• What is your evaluation of the proposal?<br class=""></blockquote><br class="">I think the alternative to simply ignore comments would be a better direction, especially since the proposal breaks code.<br class=""></div></div></blockquote><div><br class=""></div><div>Unfortunately, the alternative proposal (ignoring comments) could also break code because comments are currently treated as non-whitespace in most cases. For example, this currently works:</div><div><br class=""></div><div><font face="Courier" class="">1 /* */+2</font></div><div><br class=""></div><div>(Because the “+” has no whitespace on either side.) If comments were completely ignored, this would be an error since there is whitespace to the left of the “+” but not the right.</div><div><br class=""></div><div>If you’re interested in a more complete discussion of this direction, you can see an <a href="https://github.com/apple/swift-evolution/blob/c719adf87dae3382319e387fcf3145322a9f1239/proposals/0037-clarify-comments-and-operators.md" class="">earlier draft which proposed this in the history</a>.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" 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=""></blockquote><br class="">No.<br class=""></div></div></blockquote><div><br class=""></div><div>This is admittedly a small issue, so I can understand this point of view. The current state, though, seems pretty surprising to me — comments are treated as non-whitespace in most cases, ignored in others, and the <i class="">contents</i> of comments can affect the interpretation of the surrounding code. These are pretty clearly bugs which, to me at least, seem worth fixing.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" 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=""></blockquote><br class="">No.<br class=""><br class=""><blockquote type="cite" class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""></blockquote><br class="">Other languages ignore comments, and hence I think the alternative discussed in the proposal represents a better direction.<br class=""><br class=""><blockquote type="cite" 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=""></blockquote><br class="">Quick read.<br class=""><br class=""><blockquote type="cite" class=""><br class=""></blockquote><br class="">_______________________________________________<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></div></blockquote></div><br class=""></div></body></html>