<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=""><div class="">I can't agree that /*…*/ comments are useless. The <i class="">examples in the proposal</i> aren't things I would write, but I can certainly think of other places I use them.</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">if foo > 0 {</div><div class="">} else if foo < 0 {</div><div class="">} else /* foo == 0 */ {</div><div class="">}</div></blockquote><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">// We can't use SpecificType here because of XXX.</div></blockquote><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">let foo: protocol<OtherType/*, SpecificType*/> = bar()</div></blockquote><div class=""><br class=""></div><div class="">…and then <i class="">given</i> that we have /**/ comments in the language, we should define their behavior even in places you and I personally don't intend to write them.</div><div class=""><br class=""></div>Jordan<br class=""><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 11, 2016, at 10:32 , David Owens II 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="">+1 for the chosen path of the proposal.<br class=""><br class="">However, one alternative is to remove /* ... */ style comments all together. Every example in the proposal are examples of commenting style that really have no business in the code.<br class=""><br class="">-David<br class=""><br class=""><blockquote type="cite" class="">On Mar 11, 2016, at 10:12 AM, Dave via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class="">I’m sorta in favor… Reading the proposal, I agree that something needed to be done, but I think a better solution would’ve been to disallow comments between operators and their operands. Sorry, I didn’t see the thread about it, or I would’ve said something there.<br class=""><br class="">Anyway, if it’s this vs leaving it alone, then +1 for this.<br class=""><br class="">-Dave Sweeris<br class=""><br class=""><blockquote type="cite" class="">On Mar 11, 2016, at 12:00 PM, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> wrote:<br class=""><br class="">Hello Swift community,<br class=""><br class="">The review of “Clarify interaction between comments & operators” begins now and runs through March 15, 2016. The proposal is available here:<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0037-clarify-comments-and-operators.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0037-clarify-comments-and-operators.md</a><br class=""><br class="">Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:<br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""><br class="">or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:<br class=""><br class="">What goes into a review?<br class=""><br class="">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 class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>• What is your evaluation of the proposal?<br 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=""><span class="Apple-tab-span" style="white-space:pre"> </span>• Does this proposal fit well with the feel and direction of Swift?<br 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=""><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=""><br class="">More information about the Swift evolution process is available at:<br class=""><br class="">https://github.com/apple/swift-evolution/blob/master/process.md<br class=""><br class="">Thank you,<br class=""><br class="">-Chris<br class="">Review Manager<br class="">_______________________________________________<br class="">swift-evolution-announce mailing list<br class="">swift-evolution-announce@swift.org<br class="">https://lists.swift.org/mailman/listinfo/swift-evolution-announce<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=""></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=""></body></html>