<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-1 on “bind” for two reasons:</div><div class=""><br class=""></div><div class="">(1) Right now, variable/property declarations always use the word “let” or “var” (with the exception of the for loop iterator). That’s a nice consistency.</div><div class=""><br class=""></div><div class="">(2) It’s not clear on reading whether “bind” means “new declaration” or “alias.” It vaguely suggests I might expect this to work:</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre">        </span>let x = 1</div><div class=""><span class="Apple-tab-span" style="white-space:pre">        </span>bind y = x</div><div class=""><span class="Apple-tab-span" style="white-space:pre">        </span>y += 10</div><div class=""><span class="Apple-tab-span" style="white-space:pre">        </span>// x == 11</div><div class=""><br class=""></div><div class="">I do also find “if let” a bit awkward because ungrammatical of it how is — and this is doubly so for “if case” — but I don’t find “if bind" any better on this front. Ultimately, despite their English grammar illogic, “if let” and even “if let x = x” make enough programming language sense that I accepted them, took them as a Swift idioms, and got comfortable with them pretty quickly.</div><div class=""><br class=""></div><div class="">Cheers, P</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 30, 2016, at 7:50 PM, Howard Lovatt via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">+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 class=""><br class=""></div><div class=""> 1. `let x = x` is, outside of binding, an error. </div><div class=""> 2. Beginners quite rightly say "`x` already equals `x`!".<br class=""><br class="">On Friday, 29 January 2016, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="">
> On Jan 28, 2016, at 10:05 AM, Erica Sadun <<a href="javascript:;" onclick="_e(event, 'cvml', 'erica@ericasadun.com')" class="">erica@ericasadun.com</a>> wrote:<br class="">
><br class="">
> Do you realize how much confusion it would save if Swift just went with<br class="">
><br class="">
> if bind foo = bar {...}<br class="">
><br class="">
> with let semantics?<br class="">
<br class="">
I don't see how changing the keyword changes anything, no.<br class="">
<br class="">
-Joe<br class="">
_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</blockquote></div><br class=""><br class="">-- <br class=""> -- Howard.<br class=""><br class="">
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>