[swift-evolution] [Proposal draft] Use obtain let instead if let construction
carlosypunto at gmail.com
Sun Jan 8 00:45:18 CST 2017
Maybe I’m not explain correctly in email. The change is not a "guard let” replacement, instead it is a “if let” replacement.
> On 08 Jan 2017, at 07:22, Rod Brown <rodney.brown6 at icloud.com> wrote:
> 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.
> We already have a keyword and behaviour that you specify in the “guard” behaviour.
> Additionally, changing “guard” to be “obtain” would require “obtain” to be signficantly better than the “guard” wording - instead, it is significantly worse.
>> On 8 Jan 2017, at 1:46 pm, Carlos García via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 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
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution