Guard wouldn't work, because the "else" is usually on the same line as the last element.
Perhaps the answer is better commenting in IDEs? So if you select a region and hit CMD+/ Xcode will comment with /*...*/ instead of sticking a // in front of the whole line. Perhaps it could auto-expand to the complete clause if you select most of a clause in a multi-clause condition? Karl Sent from my new Email (https://itunes.apple.com/app/apple-store/id922793622?pt=814382&mt=8&ct=my_new_email) > > On Aug 19, 2016 at 1:21 am, <Rick Mann via swift-evolution > (mailto:[email protected])> wrote: > > > > > > On Aug 17, 2016, at 18:11 , Ben Rimmington <[email protected] > > (mailto:[email protected])> wrote: > > > > > >> On 18 Aug 2016, at 00:13, Rick Mann wrote: > >> > >> Is there any reason Swift can't allow a trailing comma in constructs like > >> this: > >> > >> guard > >> let a = ..., > >> let b = ..., > >> let c = ..., > >> else > >> { > >> } > >> > >> doing so makes it a bit easier to rearrange lines, and is similar to the > >> trailing comma allowed inside array and dictionary definitions: > >> > >> let a = [ 1, 2, 3, ] > > > > A similar proposal was rejected: > > > > > > <https://lists.swift.org/pipermail/swift-evolution-announce/2016-May/000171.html> > > Thanks. Hmm. The stated arguments seem to apply to tuples and parameter > lists, not variable bindings. > > -- > Rick Mann > [email protected] > > > _______________________________________________ > swift-evolution mailing list (mailto:[email protected]) > [email protected] (mailto:[email protected]) > https > (mailto:[email protected])://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
