+1 for `bind`. I dislike the use of the same keyword for two different purposes. Also `if let x = x` is confusing for beginners (by beginners I mean beginners to Swift not to programming) since:<div><br></div><div> 1. `let x = x` is, outside of binding, an error. </div><div> 2. Beginners quite rightly say "`x` already equals `x`!".<br><br>On Friday, 29 January 2016, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On Jan 28, 2016, at 10:05 AM, Erica Sadun <<a href="javascript:;" onclick="_e(event, 'cvml', 'erica@ericasadun.com')">erica@ericasadun.com</a>> wrote:<br>
><br>
> Do you realize how much confusion it would save if Swift just went with<br>
><br>
> if bind foo = bar {...}<br>
><br>
> with let semantics?<br>
<br>
I don't see how changing the keyword changes anything, no.<br>
<br>
-Joe<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div><br><br>-- <br> -- Howard.<br><br>