<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Whoops. +swift-evolution<br><br>~Robert Widmann</div><div><br>2016/07/12 22:34、Chris Lattner <<a href="mailto:clattner@apple.com">clattner@apple.com</a>> のメッセージ:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8">You can respond on list as part of the swift team if you’d like :-)<div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 12, 2016, at 10:33 PM, Robert Widmann <<a href="mailto:devteam.codafi@gmail.com" class="">devteam.codafi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><span style="font-size:12.800000190734863px" class=""> * What is your evaluation of the proposal?</span><div class=""><br class=""></div><div class="">+1. The less optional promotion the better.</div><div class=""><br style="font-size:12.800000190734863px" class=""><span style="font-size:12.800000190734863px" class="">* Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div class=""><br class=""></div><div class="">Yes. Removing this kind of coercion has, as I understand it, long been a goal. It doesn't serve much purpose outside of being slightly more convenient at the expensive of being terribly unreadable and downright confusing to reason about.</div><div class=""><br style="font-size:12.800000190734863px" class=""><span style="font-size:12.800000190734863px" class="">* Does this proposal fit well with the feel and direction of Swift?</span></div><div class=""><br class=""></div><div class="">Yes.</div><div class=""><br style="font-size:12.800000190734863px" class=""><span style="font-size:12.800000190734863px" class="">* 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 class=""><br class=""></div><div class="">Nothing comes to mind.</div><div class=""><br style="font-size:12.800000190734863px" class=""><span style="font-size:12.800000190734863px" class="">* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br style="font-size:12.800000190734863px" class=""></div><div class=""><span style="font-size:12.800000190734863px" class=""><br class=""></span></div><div class=""><span style="font-size:12.800000190734863px" class="">Attempted an implementation last night.</span></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Jul 12, 2016 at 10:25 PM, Chris Lattner via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Swift community,<br class="">
<br class="">
The review of "SE-0123: Disallow coercion to optionals in operator arguments" begins now and runs through July 19. The proposal is available here:<br class="">
<br class="">
<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0123-disallow-value-to-optional-coercion-in-operator-arguments.md" rel="noreferrer" target="_blank" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0123-disallow-value-to-optional-coercion-in-operator-arguments.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="">
<br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class="">
or, if you would like to keep your feedback private, directly to the review manager.<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 contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br class="">
<br class="">
* What is your evaluation of the proposal?<br class="">
* Is the problem being addressed significant enough to warrant a change to Swift?<br class="">
* Does this proposal fit well with the feel and direction of Swift?<br class="">
* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class="">
* 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="">
<a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank" class="">https://github.com/apple/swift-evolution/blob/master/process.md</a><br class="">
<br class="">
Thank you,<br class="">
<br class="">
-Chris Lattner<br class="">
Review Manager<br class="">
<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="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></blockquote></body></html>