<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">Liam: ...my proposal has been marked as out of scope for swift 3.0, so we'll have to wait a month or so to bring this back up again. </div></blockquote></div><div class=""><br class=""></div><div class="">That seems reasonable, but I _would_ like to see this come up for discussion.</div><div class=""><br class=""></div><div class="">IMHO, cases such as</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Menlo" class="">let token = authorize(user?, password?, operation?)</font></div></blockquote><div class=""><br class=""></div><div class="">are a lot more compelling than any example involving a single optional. As pointed out, a single optional is pretty easy to deal with in various ways. But checking multiple values gets clumsy:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Menlo" class="">var token: AuthToken?</font></div><div class=""><font face="Menlo" class="">if let user = user, password = password, operation = operation {</font></div><div class=""><font face="Menlo" class=""> token = authorize(user, password, operation)</font></div><div class=""><font face="Menlo" class="">}</font></div></blockquote><div class=""><br class=""></div><div class="">It bothers me that the result has to be declared separately and then reset. Nested maps are even worse.</div><div class=""><br class=""></div><div class="">Garth</div><div class=""><br class=""></div></body></html>