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

For me the link is broken and your GitHub account doesn’t seem to contain a clone of Swift-Evolution. > On 8 Jan 2017, at 03:46, Carlos García via swift-evolution > wrote: > > Hi all, > > Here’s a draft proposal to change > if let construction for obtain let.

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

-1 from me. It doesn't really pay for itself. On Sun, Jan 8, 2017 at 2:26 PM, Derrick Ho via swift-evolution < swift-evolution@swift.org> wrote: > *if let *is fine the way it currently is. It may be strange to newcomers > since it is unique, but once you get used to it, it is super useful. > >

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

*if let *is fine the way it currently is. It may be strange to newcomers since it is unique, but once you get used to it, it is super useful. On Sun, Jan 8, 2017 at 7:58 AM Georgios Moschovitis via swift-evolution < swift-evolution@swift.org> wrote: > I quite really like the `if let` syntax,

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

I quite really like the `if let` syntax, feels natural to me. -1 ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution

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

-1 to obtain, unwrap and such. +1 to removing optional pattern in favor of normal if-pattern, plus removing case: if let unwrapped? = optionalValue { ... } ​ ___ swift-evolution mailing list swift-evolution@swift.org

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

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. Best Carlos > On 08 Jan 2017, at 08:11, Robert Widmann wrote: > > -1. This proposal is,

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

-1, ‘obtain' obfuscates the meaning of the “if” statement. Since it would (conceptually) introduce a new statement that is very similar to the ‘if’ statement and ‘guard’ statement it would probably cause even more confusion. Regards, Rien Site: http://balancingrock.nl Blog:

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

-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.

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

I just realized my mistake in the example, I've corrected it > On 08 Jan 2017, at 07:46, Carlos García wrote: > > Hi Javier, > > Maybe I’m not explained correctly in email. The change is not a "guard let” > replacement, instead it is a “if let” replacement. > > Best,

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

I just realized my mistake in the example, I've corrected it > On 08 Jan 2017, at 07:45, Carlos García wrote: > > Hi Rod, > > Maybe I’m not explain correctly in email. The change is not a "guard let” > replacement, instead it is a “if let” replacement. > > Best, >

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

Hi Rod, Maybe I’m not explain correctly in email. The change is not a "guard let” replacement, instead it is a “if let” replacement. Best, Carlos > On 08 Jan 2017, at 07:22, Rod Brown wrote: > > -1. > > Your proposal seems to confuse something we already have in

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

Hi Javier, Maybe I’m not explained correctly in email. The change is not a "guard let” replacement, instead it is a “if let” replacement. Best, Carlos > On 08 Jan 2017, at 05:45, Javier Soto wrote: > > Based on your examples I think you were thinking about the "guard"

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

-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”

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

Based on your examples I think you were thinking about the "guard" keyword, instead of "if"? `If let foo = bar else` is not a valid construction. `if let foo = bar { } else {}` may have been what you meant, but in this case it is clear that this is just like a regular if, combined with unwrapping

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

-1 from me, I think that it makes perfect sense the way it is. More specifically, I read `if let safe = optional` as "if optional can be unwrapped into safe, then ..." I think `obtain let` is more confusing, as it's not clear that it's a conditional from that keyword. Plus to me, "obtain" seems

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

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/-Use-obtain-let-instead-if-let-constructions.md