<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 10, 2017, at 1:51 AM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><br class=""></div><div class="">I know we can’t do much about it now, but if optional binding had used the same syntax as it does in pattern matching, we wouldn’t be having this discussion:</div><div class=""><br class=""></div><div class=""><font face="Menlo" class="">guard let x = try doSomething() catch {</font></div><div class=""><font face="Menlo" class=""> // handle error</font></div><div class=""><font face="Menlo" class="">}</font></div><div class=""><font face="Menlo" class=""><br class=""></font></div><div class=""><font face="Menlo" class="">guard let x? = doSomething() else {</font></div><div class=""><font face="Menlo" class=""> // handle when nil</font></div><div class=""><font face="Menlo" class="">}</font></div></div></div></div></blockquote><br class=""></div><div>We tried pattern-matching syntax in `if let` a while ago. It was unbelievably unpopular. We changed it back.</div><div><br class=""></div><div><br class=""></div><div>-- </div><div>Greg Parker <a href="mailto:gparker@apple.com" class="">gparker@apple.com</a> Runtime Wrangler</div><div><br class=""></div><div><br class=""></div></body></html>