-1<br><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 25, 2017 at 1:11 PM Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
> On Jan 25, 2017, at 9:47 AM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com" class="gmail_msg" target="_blank">jtbandes@gmail.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> Really? My observation from a quick test is that "a? = b" assigns b to a if a already has a value, or does nothing if it's nil. This is sort of the opposite of what's being proposed, which is that "a ?= b" should assign to a only if it does NOT have a value.<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
My mistake, I misread the proposal. What Nichi appears to be suggesting is an assignment that only happens when `b` has a value. I would hesitate to spell that `?=` since that's so similar to '? =', but perhaps it's useful, though there are many ways to spell that already.<br class="gmail_msg">
<br class="gmail_msg">
-Joe<br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>