<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=""><b class="">What is your evaluation of the proposal?</b></div><div class="">+1 for the simple reason that there is no real downside and it is consistent with existing operators.</div><div class="">If consistency is not a goal of swift then 0.</div><div class=""><br class=""></div><div class=""><b class="">Is the problem being addressed significant enough to warrant a change to Swift?</b></div><div class="">No, Problem indicates that without it that you would have a problem accomplishing something or it would be much less efficient.</div><div class="">None of the shorthand operators “solve a problem” they are just shorthand.</div><div class="">Using "a = a ?? b" instead of “a ??= b” is not much of a saver, but there are many programmers that work/think in that shorthand.</div><div class="">I generally never use any of the shorthand operators mostly because I generally avoid mutable — but even when using mutable state</div><div class="">I don’t generally type/think in shorthand when it comes to existing types of the same ilk.</div><div class="">It would actually cost me time to use them since I would have to think then type the shorthand (and I type fairly quickly) vs automatic. </div><div class=""><br class=""></div><div class=""><b class="">Does this proposal fit well with the feel and direction of Swift?</b></div><div class="">Yes</div><div class=""><br class=""></div><div class=""><b class="">If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</b></div><div class="">I have not used other languages with a similar feature for optionals.</div><div class=""><br class=""></div><div class=""><b class="">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</b></div><div class="">Read the proposal, played around in playground comparing it to similar operators that exist and compared </div><div class=""><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On 2016-02-13, at 18:32:28, Ilya Belenkiy 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 dir="ltr" class=""><span style="color: rgb(51, 51, 51); font-family: 'Helvetica Neue', Helvetica, 'Segoe UI', Arial, freesans, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: inherit;" class="">+1 for the same reason (consistent with +=)</span><br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Sat, Feb 13, 2016 at 1:29 AM Paul Ossenbruggen via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class=""><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif,'Apple Color Emoji','Segoe UI Emoji','Segoe UI Symbol';font-size:16px;background-color:rgb(255,255,255)" class="">What is your evaluation of the proposal?</span></div></div><div style="word-wrap:break-word" class=""><div class=""><font color="#333333" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" class=""><span style="background-color:rgb(255,255,255)" class="">+1 this is seems like a natural addition similar to += or other operators which assign and perform an action.</span></font></div></div><div style="word-wrap:break-word" class=""><div class=""><font color="#333333" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" class=""><span style="background-color:rgb(255,255,255)" class=""><br class=""></span></font><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif,'Apple Color Emoji','Segoe UI Emoji','Segoe UI Symbol';font-size:16px;background-color:rgb(255,255,255)" class="">Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div class=""><font color="#333333" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" class=""><span style="background-color:rgb(255,255,255)" class="">Yes.</span></font></div></div><div style="word-wrap:break-word" class=""><div class=""><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif,'Apple Color Emoji','Segoe UI Emoji','Segoe UI Symbol';font-size:16px;background-color:rgb(255,255,255)" class="">Does this proposal fit well with the feel and direction of Swift?</span></div></div><div style="word-wrap:break-word" class=""><div class=""><font color="#333333" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" class=""><span style="background-color:rgb(255,255,255)" class="">Yes.</span></font></div><div class=""><font color="#333333" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" class=""><span style="background-color:rgb(255,255,255)" class=""><br class=""></span></font><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif,'Apple Color Emoji','Segoe UI Emoji','Segoe UI Symbol';font-size:16px;background-color:rgb(255,255,255)" 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><div style="word-wrap:break-word" class=""><div class=""><font color="#333333" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" class=""><span style="background-color:rgb(255,255,255)" class="">Not found in other languages. </span></font></div></div><div style="word-wrap:break-word" class=""><div class=""><font color="#333333" face="Helvetica Neue, Helvetica, Segoe UI, Arial, freesans, sans-serif, Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol" size="3" class=""><span style="background-color:rgb(255,255,255)" class=""><br class=""></span></font><div style="word-wrap:break-word" class=""><div class=""><div class=""><div class=""><div style="word-wrap:break-word" class=""><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif,'Apple Color Emoji','Segoe UI Emoji','Segoe UI Symbol';font-size:16px;background-color:rgb(255,255,255)" class="">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span></div></div></div></div></div></div></div><div style="word-wrap:break-word" class="">Read proposal and thread.</div>_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" target="_blank" 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></div>
_______________________________________________<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></blockquote></div><br class=""></body></html>