<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=""><blockquote type="cite" class=""><ul style="box-sizing: border-box; padding: 0px 0px 0px 2em; margin-top: 0px; margin-bottom: 16px; 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; line-height: 20.48px; widows: 1;" class=""><li style="box-sizing: border-box;" class="">What is your evaluation of the proposal?</li></ul></blockquote>-1 for this. Although the proposal was initially intended for property usage, I think the most wide spread usage will be on local variables. And this will encourage use usage of var instead of let.<div class="">For example:</div><div class=""><br class=""></div><div class="">var foo = optionalOutput()</div><div class="">foo??= bar</div><div class=""><br class=""></div><div class="">vs</div><div class=""><br class=""></div><div class="">let foo = optionalOutput() ?? bar</div><div class=""><br class=""></div><div class="">The proposed ??= may create many unnecessary var usage just because they want to use the ??= shorthand.</div><blockquote type="cite" class=""><ul style="box-sizing: border-box; padding: 0px 0px 0px 2em; margin-top: 0px; margin-bottom: 16px; 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; line-height: 20.48px; widows: 1;" class=""><li style="box-sizing: border-box;" class="">Is the problem being addressed significant enough to warrant a change to Swift?</li></ul></blockquote>No, It can be implemented as a extension if needed. <div class="">We already got default value for property, default parameter value for functions, and ?? for local variable usage.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><ul style="box-sizing: border-box; padding: 0px 0px 0px 2em; margin-top: 0px; margin-bottom: 16px; 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; line-height: 20.48px; widows: 1;" class=""><li style="box-sizing: border-box;" class="">Does this proposal fit well with the feel and direction of Swift?</li></ul></blockquote>No. It’ll encourage unnecessary usage of var.<br class=""><div class=""><blockquote type="cite" class=""><ul style="box-sizing: border-box; padding: 0px 0px 0px 2em; margin-top: 0px; margin-bottom: 16px; 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; line-height: 20.48px; widows: 1;" class=""><li style="box-sizing: border-box;" class="">If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</li></ul></blockquote>The ||= operator in ruby. But the reason why ||= is popular is that ruby has no support for keyword argument before ruby 2.0. For example:</div><div class="">def foo(options={})</div><div class=""> options[:bar]||=“default”</div><div class="">end</div><div class="">using ||= is the de factor way to set value to options[:bar]</div><div class=""><br class=""></div><div class="">but after ruby 2.0 following method is preferred</div><div class=""><br class=""></div><div class="">def foo(bar: “default”)</div><div class="">end</div><div class="">which eliminates the need of ||= operator </div><div class=""><blockquote type="cite" class=""><ul style="box-sizing: border-box; padding: 0px 0px 0px 2em; margin-top: 0px; margin-bottom: 16px; 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; line-height: 20.48px; widows: 1;" class=""><li style="box-sizing: border-box;" class="">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</li></ul></blockquote><div class="">Read though the origin thread, read the proposal, read some of the reviews.</div><div class=""><br class=""></div>John<br class=""><div class=""><br class=""></div></div></div></body></html>