<div dir="ltr">What about an additional method? No subscripting, just a method that throws instead of trapping?</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 28, 2016 at 2:08 PM, Dave Abrahams 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"><span class=""><br>
on Thu Jun 23 2016, "L. Mihalkovic via swift-evolution" <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
<br>
>> On Jun 23, 2016, at 6:07 PM, Pranjal Satija via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
>><br>
>> Would modifying array subscripts to return implicitly unwrapped<br>
>> optionals be a bad idea? This way, if an array is indexed out of<br>
>> bounds,<br>
><br>
> Most out of bounds errors originate in bad code. So now instead of<br>
> forcing people to rewrite it or at least have more bad code to be more<br>
> defensive, this would give an incentive to ignore the original problem<br>
> and never learn to code properly.<br>
<br>
</span>+1; I am opposed to this. If it's not already on the list of<br>
commonly-rejected proposals, I'm surprised, as it comes up often.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Dave<br>
</font></span><div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br></div>