Perhaps that was the original idea (guard as a multithreaded statement) since in iOS your code and the UI run on different threads. Anyway, I'd still stick with guard as I don't think this is confusing enough to justify a change.
On Tuesday, 21 June 2016, James Campbell via swift-evolution < [email protected] <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > I think unless has always made more sense, guard felt like a multithreaded > statement as in guard this variable from other threads. > > *___________________________________* > > *James⎥Head of Trolls* > > *[email protected]⎥supmenow.com <http://supmenow.com>* > > *Sup* > > *Runway East * > > *10 Finsbury Square* > > *London* > > * EC2A 1AF * > > On 21 June 2016 at 09:14, Rimantas Liubertas via swift-evolution < > [email protected]> wrote: > >> >> In summary, “require … else” is a very clean choice and beats “guard ... >>> else” handily. >>> >> >> For you maybe. I prefer quard—it carries slightly different semantic load >> and fits more cases, imho. >> >> r. >> >> _______________________________________________ >> swift-evolution mailing list >> [email protected] >> https://lists.swift.org/mailman/listinfo/swift-evolution >> >> > -- L
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
