Don't remove tuples. <br>They make it very convenient to pass multiple values around.<br><br>Tuples use .0 instead of [0] which prevents any index out of bounds issues at compile time rather than at run time.<br><br>Tuples should not adopt a dictionary style access because dictionaries imply nil for any key that doesn't exist in the dictionary. Tuples syntax prevents you from using non-existent keys.<br><br><br><div class="gmail_quote"><div dir="ltr">On Sun, Jan 8, 2017 at 1:51 AM David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
<br class="gmail_msg">
> On Jan 7, 2017, at 19:34, Freak Show <<a href="mailto:freakshow42@mac.com" class="gmail_msg" target="_blank">freakshow42@mac.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> I think you're missing the forrest for the trees here.'<br class="gmail_msg">
><br class="gmail_msg">
> Let me ask this: if you remove tuples from the language - what have you lost - really? You can still say everything you could before.<br class="gmail_msg">
<br class="gmail_msg">
A really convenient way to pass around multiple values without having to bother with a formal struct.<br class="gmail_msg">
<br class="gmail_msg">
- Dave Sweeris<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>