<div dir="ltr">Interesting, I think I misread it too. The one I was thinking of is the same as the rejected proposal: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0024-optional-value-setter.md">https://github.com/apple/swift-evolution/blob/master/proposals/0024-optional-value-setter.md</a><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Wed, Jan 25, 2017 at 10:11 AM, Joe Groff <span dir="ltr"><<a href="mailto:jgroff@apple.com" target="_blank">jgroff@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
> On Jan 25, 2017, at 9:47 AM, Jacob Bandes-Storch <<a href="mailto:jtbandes@gmail.com">jtbandes@gmail.com</a>> wrote:<br>
><br>
> 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>
<br>
<br>
</span>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>
<span class="gmail-HOEnZb"><font color="#888888"><br>
-Joe<br>
<br>
</font></span></blockquote></div><br></div></div>