<div dir="ltr">Hey Sean,<div><br></div><div>Jordan Rose answered this question yesterday in a different discussion:</div><div><a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/002425.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/002425.html</a><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 15, 2015 at 1:08 PM, Sean Kosanovich via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all!<br>
<br>
I have been using Swift nearly exclusively for iOS projects since its release (for better or worse). I love the fact that a compiling application gives me some sort of guarantee that I won’t encounter a nil reference (unless of course I ignore optionals and force unwrap them…not a great idea).<br>
<br>
When pulling values out of a Dictionary, we get an Optional value which makes perfect sense. Why does this not extend out to Arrays? There is no guarantee that when I am pulling the 8th element out, that it will have a valid value.<br>
<br>
It seems odd to me that Optionals are a fundamental part of the language but they don’t extend to Arrays.<br>
<br>
Thanks,<br>
Sean<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br></div>