<div dir="ltr"><div><br></div><div><span style="font-size:13px"> • What is your evaluation of the proposal?</span></div><div>+1</div><div><br><span style="font-size:13px"> • Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div>Yes</div><div><br><span style="font-size:13px"> • Does this proposal fit well with the feel and direction of Swift?</span></div><div>Yes. <br style="font-size:13px"><span style="font-size:13px"> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span></div><div><span style="font-size:13px"> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br></div><div>`=` vs `==` is a common and subtle case. I consider the all of the comparison operators and our overloads thereof to be the most compelling argument in favor of this change. It only occurred to me recently that I should add `@warn_unused_result` on *every* custom implementation of `==` and `<` This proposal remedies that problem. <span style="font-size:13px"><br></span></div><div><span style="font-size:13px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 16, 2016 at 1:36 PM, Chris Lattner via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Swift community,<br>
<br>
The review of “Defaulting non-Void functions so they warn on unused results” begins now and runs through March 21, 2016. The proposal is available here:<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0047-nonvoid-warn.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0047-nonvoid-warn.md</a><br>
<br>
Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:<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>
<br>
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>
<br>
What goes into a review?<br>
<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>
• What is your evaluation of the proposal?<br>
• Is the problem being addressed significant enough to warrant a change to Swift?<br>
• Does this proposal fit well with the feel and direction of Swift?<br>
• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
More information about the Swift evolution process is available at:<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a><br>
<br>
Thank you,<br>
<br>
-Chris<br>
Review Manager<br>
<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">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><br></div>