<div dir="ltr">The diff might be helpful as well:<div><br></div><div><a href="https://github.com/apple/swift-evolution/commit/5015578c019818234f1b33d82ad96b94cb444b1b?short_path=3a8f57a#diff-3a8f57ac6db03a3be35cb05972e95d69">https://github.com/apple/swift-evolution/commit/5015578c019818234f1b33d82ad96b94cb444b1b?short_path=3a8f57a#diff-3a8f57ac6db03a3be35cb05972e95d69</a></div><div class="gmail_extra">
<br><div class="gmail_quote">On Mon, Apr 25, 2016 at 4:35 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>
Steve opted to revise his original proposal in order to incorporate great feedback from the original review period. As such, we’re extending the review period in order to get adequate consideration of his new changes. The extended review of "SE-0067: Enhanced Floating Point Protocols" runs through April 29. The proposal is available here:<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0067-floating-point-protocols.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0067-floating-point-protocols.md</a><br>
<br>
His previous revision is available here:<br>
<br>
<a href="https://github.com/apple/swift-evolution/blob/fb1368a6a5474f57aa8f1846b5355d18753098f3/proposals/0067-floating-point-protocols.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/fb1368a6a5474f57aa8f1846b5355d18753098f3/proposals/0067-floating-point-protocols.md</a><br>
<span class="im HOEnZb"><br>
Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:<br>
<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.<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>
</span><span class="im HOEnZb"> * What is your evaluation of the proposal?<br>
</span><span class="im HOEnZb"> * Is the problem being addressed significant enough to warrant a change to Swift?<br>
</span><span class="im HOEnZb"> * Does this proposal fit well with the feel and direction of Swift?<br>
</span><span class="im HOEnZb"> * If you have you used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
</span><span class="im HOEnZb"> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
</span><span class="im HOEnZb">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 Lattner<br>
Review Manager<br>
<br>
</span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div></div>