<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="">Hey all,</div><div class=""><br class=""></div><div class="">As usual, apologies if this horse was beaten ages ago before I joined the mailing list, but thought I would bring this up.</div><div class=""><br class=""></div><div class="">I was typing the above (for the hundredth time) the other day and I was wondering whether it might be worth considering offering a shorter syntax:</div><div class=""><br class=""></div><div class=""><font face="Courier" class="">guard let x, y, z else {…}</font></div><div class=""><br class=""></div>I was never convinced why implicit nil checks (i.e. if x {…}) were such a bad thing. But now in Swift it seems that it would be much more convenient to be able to simply skip the assignment part of the expression and define the above as guaranteeing and unwrapping x, y and z in the appropriate scope.<div class=""><br class=""></div><div class="">I think with such powerful and already compact expressions now wanting to get on the same line,adding this would make the language even more compact and elegant. It could be added as a non-source-breaking change, still allowing x = x for those who prefer it, but could significantly tighten up such uses, which I’m finding are ubiquitous in my code.</div><div class=""><br class=""></div><div class="">Any thoughts?</div><div class=""><br class=""></div><div class="">-d</div><div class=""><br class=""></div></body></html>