<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="">Hi Rod,</div><div class=""><br class=""></div><div class="">Maybe I’m not explain correctly in email. The change is not a "guard let” replacement, instead it is a “if let” replacement.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Carlos</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On 08 Jan 2017, at 07:22, Rod Brown <<a href="mailto:rodney.brown6@icloud.com" class="">rodney.brown6@icloud.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">-1.</div><div class=""><br class=""></div><div class="">Your proposal seems to confuse something we already have in the language to handle unwrapping and guarding, to only proceed if the item is non-null: Guard.</div><div class=""><br class=""></div><div class="">We already have a keyword and behaviour that you specify in the “guard” behaviour.</div><div class=""><br class=""></div><div class="">Additionally, changing “guard” to be “obtain” would require “obtain” to be signficantly better than the “guard” wording - instead, it is significantly worse.</div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 8 Jan 2017, at 1:46 pm, Carlos García 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><pre style="font-variant-ligatures: normal; orphans: 2; widows: 2;" class=""><span style="white-space: pre-wrap;" class="">Hi all,
Here’s a draft proposal to change <b class="">if let</b> construction for <b class="">obtain let</b>. Proposal is at:</span></pre><pre style="font-variant-ligatures: normal; orphans: 2; widows: 2;" class=""><a href="https://github.com/carlosypunto/swift-evolution/blob/obtain-let-instead-if-let/proposals/XXXX-Use-obtain-let-instead-if-let-constructions.md" class="">https://github.com/carlosypunto/swift-evolution/blob/obtain-let-instead-if-let/proposals/XXXX-Use-obtain-let-instead-if-let-constructions.md</a><span style="white-space: pre-wrap;" class="">
I would like to see what you think and get help with "<i class="">Effect on ABI stability</i>" and "<i class="">Effect on API resilience</i>" points
Carlos</span></pre><pre style="font-variant-ligatures: normal; orphans: 2; widows: 2;" class=""><span style="white-space: pre-wrap;" class=""><br class=""></span></pre></div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></body></html>