<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 Robert,</div><div class=""><br class=""></div><div class="">ok, I agree with you `obtain` could be bad replacement, that's why it's a draft. I’m not a native english speaker.</div><div class="">In any case I’ve not problem the way it is now. </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 08:11, Robert Widmann <<a href="mailto:devteam.codafi@gmail.com" class="">devteam.codafi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">-1. This proposal <i class="">is</i>, in fact, cosmetic and has no impact on matters related to the ABI. Moreover it is a breaking change that would require migration of a <i class="">lot</i> of existing code without significant justification. </div><div class=""><br class=""></div><div class="">A verb in this position is far more confusing than a logical connective. `obtain` and similar imply that the statement attempts to move a value out of a container, which is perhaps the wrong image here, and does not elucidate control flow. "So I've obtained a value, what then? Where does the flow of control reach next?" </div><div class=""><br class=""></div><div class="">If beginners are confused about the optional unwrapping process, even after reading the many parts of the Swift book that offer examples of its use cases and semantics, then I would be more concerned. But I'm not inclined to believe it's enough to warrant a change this large at this time.</div><div class=""><br class=""></div><div class=""><div class="">~Robert Widmann</div></div><div class=""><br class="">2017/01/07 19:46、Carlos García via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> のメッセージ:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" 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></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">swift-evolution mailing list</span><br class=""><span class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a></span><br class=""><span class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br class=""></div></blockquote></div></div></blockquote></div><br class=""></body></html>