-1. 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@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 > > Carlos > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
