<div dir="ltr">Yes I understand but I was still able to miss the fact a variable imported from objective C as a !.<div><br></div><div>Take this example:</div><div><br></div><div>//Imported From Obj-C Library</div><div>typealias MyClosure = (value: NSObject!) -> Void</div><div><br></div><div>func loadData(block: MyClosure)</div><div><br></div><div>//Implemented In Swift File else where</div><div>loadData {</div><div> value in</div><div> print(value) //Crashes if we try to access it</div><div>}</div><div><br></div><div>This would be clearer to me:</div><div><br></div><div><div>//Imported From Obj-C Library</div><div>typealias MyClosure = (value: NSObject!) -> Void</div><div><br></div><div>func loadData(block: MyClosure)</div><div><br></div><div>//Implemented In Swift File else where</div><div>loadData {</div><div><br></div><div>//Since the property is a unwrapped optional, the compiler enforces us to use the ! after the variable name</div><div> value! in</div><div> print(value!) //Still crashes if we try to access it but at least we know its an un-wrapped type.</div><div>}</div></div><div><br></div><div>This has happened to me a few times with Librarys in Objective-C and I have released an app that crashed because of that reason.</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">
<p><b><font color="#cc0000">___________________________________</font></b></p><p><b>James⎥Head of Trolls</b></p><p><b><font color="#cc0000"><a href="mailto:james@supmenow.com" target="_blank">james@supmenow.com</a>⎥<a href="http://supmenow.com" target="_blank">supmenow.com</a></font></b></p><p><b><font size="2">Sup</font></b></p><p><b><font size="2">Runway East
</font></b></p><p><b><font size="2">10 Finsbury Square</font></b></p><p><b><font size="2">London</font></b></p><p><b><font size="2">
EC2A 1AF </font></b></p></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Mar 9, 2016 at 8:23 PM, Brent Royal-Gordon <span dir="ltr"><<a href="mailto:brent@architechies.com" target="_blank">brent@architechies.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> I would love to take a page out of Ruby's book which has ! for things that are dangerous and ? for boolean expression. Instead for Swift we could have ? for optional returns and ! for forced unwrapped.<br>
><br>
> So we would have:<br>
><br>
> Object()<br>
> OptionalObject?()<br>
><br>
> value<br>
> optionalValue?<br>
> forcedUnwrappedValue!<br>
><br>
> function()<br>
> optionalFunction?()<br>
> forcedUnwrappedValue!()<br>
><br>
> optionalProtocolMethod?()<br>
> forcedProtocolMethod!()<br>
<br>
</span>You do understand that `?` at the end of a symbol already means something else, don't you? That's how optional chaining works.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Brent Royal-Gordon<br>
Architechies<br>
<br>
</font></span></blockquote></div><br></div>