[swift-evolution] [Proposal draft] Use obtain let instead if let construction

Carlos García carlosypunto at gmail.com
Sun Jan 8 01:24:35 CST 2017

Hi Robert,

ok, I agree with you `obtain` could be bad replacement, that's why it's a draft. I’m not a native english speaker.
In any case I’ve not problem the way it is now. 


> On 08 Jan 2017, at 08:11, Robert Widmann <devteam.codafi at gmail.com> wrote:
> -1.  This proposal is, 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 lot of existing code without significant justification.  
> 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?"  
> 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.
> ~Robert Widmann
> 2017/01/07 19:46、Carlos García via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> のメッセージ:
>> Hi all,
>> Here’s a draft proposal to change if let construction for obtain let. Proposal is at:
>> https://github.com/carlosypunto/swift-evolution/blob/obtain-let-instead-if-let/proposals/XXXX-Use-obtain-let-instead-if-let-constructions.md <https://github.com/carlosypunto/swift-evolution/blob/obtain-let-instead-if-let/proposals/XXXX-Use-obtain-let-instead-if-let-constructions.md>
>> I would like to see what you think and get help with "Effect on ABI stability" and "Effect on API resilience" points
>> Carlos
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170108/21ea5b23/attachment.html>

More information about the swift-evolution mailing list