<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="">On Jul 19, 2016, at 3:46 PM, Saagar Jha <<a href="mailto:saagarjha28@gmail.com" class="">saagarjha28@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I have updated the proposal <a href="https://gist.github.com/saagarjha/f33fecd4576f40133b6469da942ef453" class="">here</a>. Since this is a potentially a source breaking change, I’d like this to be considered for Swift 3; unless anyone has any issues with it, I’m going to push this to swift-evolution.</div></div></blockquote><div><br class=""></div><div>Some comments:</div><div>- The syntax proposed would be *completely* unlike anything in Swift, and is semantically changing things unrelated to the type.</div><div>- This proposal doesn’t work, and overly punishes IUOs.</div><div><br class=""></div><div>I recommend that we do not discuss this proposal, as it would not be a good use of community time. Beyond the unworkability of this specific proposal, in my personal opinion, there is nothing wrong with the T! syntax. Making it significantly more verbose would be a very *bad* thing for the intended use cases.</div><div><br class=""></div><div>-Chris</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""><div class="">
<div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Saagar Jha<br class=""><br class=""><br class=""></div>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">On Jul 5, 2016, at 13:30, Saagar Jha <<a href="mailto:saagarjha28@gmail.com" class="">saagarjha28@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Gave me a chuckle, but yeah, basically.</div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Tue, Jul 5, 2016 at 12:54 PM William Jon Shipley <<a href="mailto:wjs@delicious-monster.com" class="">wjs@delicious-monster.com</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="">On Jun 30, 2016, at 9:22 AM, Saagar Jha via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>> wrote:<br class=""><div class=""><blockquote type="cite" class=""><span style="font-family:HelveticaNeue;float:none;display:inline!important" class="">When I see an IUO property, I consider it a sort of “contract”–it’s basically saying something like “I can’t set this to a valid value right now, but by the time you use it I promise that it’s non </span><code class="">nil</code><span style="font-family:HelveticaNeue;float:none;display:inline!important" class="">”</span></blockquote></div><br class=""></div><div style="word-wrap:break-word" class=""><div class="">You might say that an IUO is sort of an IOU?</div></div><div style="word-wrap:break-word" class=""><div class=""><br class=""></div><div class="">-W</div></div></blockquote></div><div dir="ltr" class="">-- <br class=""></div><div data-smartmail="gmail_signature" class=""><div dir="ltr" class="">-Saagar Jha</div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></body></html>